Zugg Software :: View topic - [2.09] Another Editor-DB synchronization issue

Enchanter Joined: 09 Sep 2007 Posts: 605

Another problem with synchronization - this time with my beloved buttons.

All steps except 8 can be performed in the untitled session.

1) Open CMUD, hit Esc, open the editor.
2) Create a button, give it any caption you like.
3) Switch button type to Toggle (you may switch to Multistate as well), switch to Options tab (this will add "State 1" row in the Tree view), but do not type anything for newly created State 1. Instead, click on the button name in the tree or on any other setting in the tree view. The "State 1" row will be removed from the tree view (CMUD consider that user has changed his mind and do not want the button to have an additional state).
4) Select New->Add New Button state to add second button state again. I must point that at first time it is very hard, may be impossible, to realize that you can add a new button state from the New drop-down button, because at normal conditions that menu item is not visible and people may be just not aware of its existence. Ok, add new button state and again, do not type anything, just click on any other setting in tree view to remove "State 1" row from the tree.
5) Repeat step 4 as many times as you want, but even 1 time is enough.

6) Switch to XML tab and see garbage left from each step 4 repetition (<state color="black"></state>...)
7) Now add second button state for true and choose any color you like. Close the editor and test your button. You will see that in the new state the button has black background no matter what color you chose.

8) This step can't be performed in the untitled session, because it requires CMUD restart. After restart, if you tried to do all the steps in your session, not in the untitled, you will see that in DB all settings was stored correctly, without any garbage. So there is a issue on how the Editor handles adding/removing button states from cache.

Posted: Mon Oct 29, 2007 8:53 pm

OK, I think I fixed the main problem here. The main problem is that CMUD isn't supposed to delete the button state in step 3. Blank button states are allowed, so I have fixed that.

Posted: Tue Oct 30, 2007 6:13 am

I think he means how the options on the New menu for trigger and button states aren't there until you have a trigger or a button selected and click the menu. Someone (especially someone expecting a format similar to zMUD, where trigger states are on a tab of the original trigger) might be confused as to how they create a new state.

Enchanter Joined: 09 Sep 2007 Posts: 605

Someone...

First time I was confused myself so much that I wrote a message to support.

Thanks, Fang, you've find the right words to make it clear... as always. Mr. Green

Enchanter Joined: 09 Sep 2007 Posts: 605

I suggest not to hide "Add new state" menu item but rather set its Enabled or like property to false (grayed).

Posted: Tue Oct 30, 2007 9:00 pm

Ahh, ok, I see what you are saying. I supposed I could make the menu option visible and just disable it (and change it to something generic like "Add new child state" when you aren't editing a trigger or button).