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

1. When grabbing variables and functions from the toolbar in the function editor, you have to click the small \/ next to the icon to get the menu. whereas on operators and comparisons you can click the big button. Clicking the big button on the prior doesn't do anything. It gets me all of the time.

[HL]2. When grabbing icons from the toolbar, its too easy to drop them into the abyss. It looks as if, as they pass over the small-informative-text icon, that pops up once you click to select the item from the menu, the software sees that as passing over an outer edge of the workspace, and drops it. Numbers do it mostly. In general, losing grabbed icons gets annoying as I have horrible coordination and my mouse goes all over the place (not really, but I do drop the icons off of the edge a lot). It's like the out-of-bounds recieving rule in football. But in this case what would it hurt to maintain posession of the icon on an out of bounds? It's probably how you have implemented the entire functionality, so if it's not changable, ...eh.[/HL]

[HL]3. Copy and Paste in both graphics and logic? Maybe? One day? It would save a bunch of time. But there are things to consider like renaming objects that require unique names.
[/HL]

4. I'd like to be able to name those inputs in functions (not root functions) maybe you can protect vs. bad recursives another way? If not, no big deal.(The designer would have to know to combine same-named input references in the "input order area"....
EDIT:scratch that, you have the functionality there already...It's the menu V arrow to the right of the button. Staring me right in the face the whole time. Excellent.
Might as well replace this one with an Anti-Then for general root functions.

[HL]5. Are you ever going to activate the extensive 'help' documentation that I KNOW you've been sitting on?[/HL]

6. In the (not root)function builder labels are invisible regardless of the state of the label button?

7. Multiple virtual brains.

[HL]8. With analog assignment functions (and some others as well) logic could be utilized to manipulate or zero or whatever signals as they pass to variables, and even between variables, if numeric operators would treat true/false or on/off as 1/0. Many possiblities would open up with this (including many I'm itching to implement).[/HL]

[HL]9. ln(x) please?[/HL]
[HL]
10. Perhaps you could have the configurator write the code that it doesn't recognize to a buffer, and have it offer it to you (*.txt?) before a save operation, so that it doesn't get accidentally lost. [/HL]

Ten's good for now. I know I've forgotten a few though.

[HL]I don't think that I've ever seen the pushed state while pushing a button in MDX. I've been using some pretty distinct colors, just to be certain, but I have yet to see it.[/HL]

MDX Configurator still generates the closing comment <!--End Display Buttons --> at the end of the multi_image section in the xml code, where it should probably read <!--End Multi Images --> and since that's hardcoded, my numerous attempts to correct it have failed.

Configurator has a problems with the way it sorts multi_images. It appears to be sorting like 0,1,10,110,111,...,119,12,...,199,2...

Originally Posted by 2k1Toaster

You mean for the auto import? It does it by filename. That is why all the multiimages are labelled as 001, 002, 003... 010, 011, 012...that sort of thing.

That is a windows problem. If it is alphabetical, it will do it that way. MDX doesnt sort, it relies on windows' name sort.

Ah, then windows must have got rid of the preceding zeros in the names then (from the ones you named). Isn't that nice. Or maybe during compress/decompress. Anyway, the arc drawings I have in content/images/multi_images/ from the default skin are named 1,2,3 not 001,002,003. I'll rename them and try again then.

Thanks



hmmm, is it just me?