Thread: Fusion Control Centre Uber Edition -- Need Testers

Originally Posted by bratnetwork

Wow! This new version seems like it has many new awesome and useful features! I already can't get myself away from it trying to figure out the new skinning and programming.

Question: How do code a PAGE button? Also do the "button id"s matter what they are called?

comme ca:

Code:

<button id="IncrementPage" enabled="yes" function="change page" functionTargetID="RequiredFiller" vote_opinion="+1" vote_priority="medium">

the voteopinion again can be either a number (like change to page 2) or it can be a change (like go to next page, or go to the 2nd next page). And the pages work in my version that is new as of like 6am, but not the one for download. So right now page buttons do nothing in your version. I will update it again in a few hours after some curried chicken and roti. yummmmmm

And the button ID's absolutely have to be unique. If it is not unique, the button will not be added. The only thing it is used for is tying in logic commands to the state of a button rather than an input, as well as internally to decide what button has been clicked.

Originally Posted by bratnetwork

Also no matter how you type you button text it always comes out all lower case in the program

Yeah I noticed that too. Easy fix. I made everything convert to lower case so that "functionTargetID" is the same as "functiontargetid" and "FuNcTiOnTaRgEtId". Less typos due to case.



Also for future reference, I dont get an email when you edit a post. I only get one when you make a new post. So if you are editing your post to add more info, do the post whore thing and make a new post so I get an email. Thanks.

Originally Posted by 2k1Toaster

comme ca:

Code:

<button id="IncrementPage" enabled="yes" function="change page" functionTargetID="RequiredFiller" vote_opinion="+1" vote_priority="medium">

I saw what you posted in comments/suggestions, and I agree with you on the code tags!

Originally Posted by 2k1Toaster

Yeah I noticed that too. Easy fix. I made everything convert to lower case so that "functionTargetID" is the same as "functiontargetid" and "FuNcTiOnTaRgEtId". Less typos due to case.

Just keep us updated on what will end up being case-sensative and what will not please.

Originally Posted by 2k1Toaster

Also for future reference, I dont get an email when you edit a post. I only get one when you make a new post. So if you are editing your post to add more info, do the post whore thing and make a new post so I get an email. Thanks.

Post-whore it is then...


Can you explain the following section of code from the beginning of your <all statements> section?

I'm not sure I'm getting it fully.

Code:

<if priority="medium" fire_on="logic">
   <parameter1>
      <variable do="set" name="is5greaterthan3">
         <if>
            <parameter1>
               <number>5</number>
            </parameter1>
            <test check="greater than or equal to"></test>
            <parameter2>
               <number>3</number>
            </parameter2>
         </if>
      </variable>
   </parameter1>
   <test check="NAND"></test>
      <parameter2>
         <boolean_operation type="NOT">
            <parameter1>
               <boolean_operation type="OR">
                  <parameter1>
                     <variable do="get">is5greaterthan3</variable>
                  </parameter1>
                  <parameter2>
                     <boolean>false</boolean>
                  </parameter2>
               </boolean_operation>
            </parameter1>
         </boolean_operation>
      </parameter2>
</if>

Ok newest version with Text that is any case, and then the page buttons work along with an update in the sample file. A single button can be on multiple pages by just adding another page attribute somewhere in the button.

Link to newest download:
RAR: http://www.fusioncontrolcentre.com/T...er20071122.rar
ZIP: http://www.fusioncontrolcentre.com/T...er20071122.zip

Originally Posted by h3rk

Just keep us updated on what will end up being case-sensative and what will not please.

Nothing is case sensitive at all right now. Every tag name and attribute is converted to lowercase before parsing what it is. So no matter how you type it comes out all lower case. I removed the lower case conversion for the text so it wont do that for the textprimary, textsecondary, and textdisabled.

Originally Posted by h3rk

Can you explain the following section of code from the beginning of your <all statements> section?

I'm not sure I'm getting it fully.

Code:

<if priority="medium" fire_on="logic">
   <parameter1>
      <variable do="set" name="is5greaterthan3">
         <if>
            <parameter1>
               <number>5</number>
            </parameter1>
            <test check="greater than or equal to"></test>
            <parameter2>
               <number>3</number>
            </parameter2>
         </if>
      </variable>
   </parameter1>
   <test check="NAND"></test>
      <parameter2>
         <boolean_operation type="NOT">
            <parameter1>
               <boolean_operation type="OR">
                  <parameter1>
                     <variable do="get">is5greaterthan3</variable>
                  </parameter1>
                  <parameter2>
                     <boolean>false</boolean>
                  </parameter2>
               </boolean_operation>
            </parameter1>
         </boolean_operation>
      </parameter2>
</if>

ok it is a big if statement. That entire thing needs to evaluate to true before what will be in the "then" area is evaluated. As of right now, nothing is in the "then" area.

So here is the equivalence:

Code:

         <if>
            <parameter1>
               <number>5</number>
            </parameter1>
            <test check="greater than or equal to"></test>
            <parameter2>
               <number>3</number>
            </parameter2>
         </if>

if(5 >= 3) which obviously evaluates to true, but was done for testing not actual use! Then

Code:

<variable do="set" name="is5greaterthan3">
   ...
</variable>

Takes whatever inside of it and stores it as a variable with name of "is5greaterthan3". If the variable exists, it will override the current value. If the variable does not exist, it will create it. So in this case the variable "is5greaterthan3" is "true".

Code:

<boolean_operation type="OR">
                  <parameter1>
                     <variable do="get">is5greaterthan3</variable>
                  </parameter1>
                  <parameter2>
                     <boolean>false</boolean>
                  </parameter2>
               </boolean_operation>

this makes the operation "true OR false" because is5greaterthan3 is true and then false is obviously "false". The type is OR which is a logic inclusive OR. Meaning if any input is true, then the output is true. So that expression with "true OR false" evaluates to true.

Then the big all encasing if says "true NAND true" and the outcome of that is of a medium priority. And there are 4 timers remember, the gui, input, output, and logic. So when the logic timer fires, this if statement is evaluated. If fire_on was "gui" for isntance, then when the logic timer ticks, it would ignore this entire if/then completely.

thanks, that clears things up nicely. I'm trying to set up "radio-button" functionality with 6 buttons. The buttons are tied to boolean variables.
Once I get my radio-button-function statement(s) set up, I should set the encasing statement to fire on gui (because it deals with the graphics)?

Concerning the following:

Originally Posted by 2k1Toaster

Now the logic portion is sort of like programming in my own little xml based language. I think it is intuitive. And you can create functions to make the code less repetitive. Each analogue port can store a user settable number of history points too. So an averager of time 0 and time 1, would be to add then and divide by 2 type thing. However averaging over any "n" number of points is built in already.

and

Code:

<parameter1>
   <evaluate function="thermometer">
      <input order="1">
         <analogue id="Outside Temp" time="0"></analogue>
      </input>
   </evaluate>
</parameter1>

What is "<input order="1">" for?

Can I put a variable as the value for the 'time' property?

How do I average here (can the value be an expression)?

Analogues actually average by themselves already if wanted.

But time cannot be a variable.

And input order 1 is because in the cooresponding function, there is an input with an order of 1 as input parameter.

Originally Posted by 2k1Toaster

Analogues actually average by themselves already if wanted.

But time cannot be a variable.

And input order 1 is because in the cooresponding function, there is an input with an order of 1 as input parameter.

I see now, there's that thermometer function xml page in the config file. I'm not sure how that works; the reference to it, as a whole, or the thermometer function itself.

it searches for function that has a matching name. If it finds one, it parses that function. But first it needs to get the inputs to the function. In this case all it does it take the voltage of an input and returns the temperature in celcius. So for each sensor we will have something like that.