Thread: Fusion Control Centre MDX Suggestions, Bugs, and Comments

Time to get my axe out and chop my logic in half!!!

I was building some multi-images and I noticed something. By default, the configurator places all multi-images directly in the MDX\Content\Images\multi_images directory. And in order for the auto-importer to work correctly, images need to be numbered a certain way (see where I'm going here?). Once more than one image is used, there is a strong risk of overwriting image files. Each multi-image should be made in a sub-folder(named same as multi-image?), where each multi-image can follow the needed file numbering scheme without concern. Of course this can be done properly when writing with the xml skin code directly, so this is another configurator request, I suppose.

I don't know how practical it may be, but is it possible for labels to have a suffix option, so if a label refers to a variable that is numeric but represents temperature it can be "78 F" instead of "78". (F,C,%,kw/m^2,V,etc.)

Just to elaborate on the multi-image issue, I created my own subfolders with 000,005,010...100 named files, and I have 000,001...240 files in the main multi-image folder. I manually set up each new multi-image so that they reference the files in the new subfloder and everything works great. But, once I open the skin in the configurator, edit anything, and then save the skin, the file-path for the new multi-image drops the subfolder part, and references the wrong images that are directly in the multi-image folder. I've fixed it several times now, because nothing beats the configurator for setting up the graphics.

Here's another one. I can describe the problem, but I'm not sure about the answer.

Take this button for an example:

Code:

      <button id="Btn_Temp_Lower" enabled="yes" function="change variable" functionTargetID="variable_test_lower1" vote="attached" vote_opinion="+1" vote_priority="Low">
        <images imagePrimary="content\images\button_images\Btn_Down_Temp_Dk.png" imageSecondary="content\images\button_images\Btn_Down_Temp_Lt.png" imageDisabled="content\images\button_images\Blank.png" imagePushed="content\images\button_images\Btn_Down_Temp_Lt.png"></images>
        <display size="138,45" location="330,452" page="2" z_order="0"></display>
        <vote_options minimum_delta_vote_time_down="20" minimum_delta_vote_time_up="20"></vote_options>
        <up_click up_click_function="change variable" up_click_functionTargetID="variable_test_lower1" up_click_vote_opinion="+0" up_click_vote="attached" up_click_vote_priority="High"></up_click>
      </button>

This button is momentary. You push it, it makes an intermediate variable go to 1 (incrementing another variable in logic), let go and the variable goes to 0.

So what would you expect for the image displayed?

Primary- unpushed image
Secondary- pushed image(but, I suppose I could change this to unpushed image)
Pushed- pushed image.

The button toggles between secondary and primary on every push. This would make sense if it were attached to an output, or to a variable that doesn't toggle back on upclick, but as it stands it does not make sense.

Since it functions correctly, I suppose I can just change the secondary image to the same as the primary, but that seems like a work around. And if I do, I will never see the pushed state, since "pushed state" doesn't work for me.

This one is more of a feature request. One that I can work around if need be with multi-images and transparent buttons:

I have 3 outputs that I need to send a pulse to. I'm simulating pushing a button. The electronics that I'm interfacing reacts to this "button-press" by latching on one of it's outputs. I have 3 inputs tied to these latched outputs of the interfaced electronics.
I think it would be just peachy if somehow I could tie the state of the button to a variable that is independant of it's output.

That way the button, while it sends the necessary pulses, accurately portrays the state of what it is indirectly turning on.

(As an option, not to change the way things are. If possible).

EDIT: In fact, with the multi_image/clear button approach, I could even patch the pushed image thing for all of my momentary buttons that do +1 - Upclick and +0 Downlclick.