|
forren Novice
Joined: 26 Apr 2007 Posts: 44
|
Posted: Tue Jul 03, 2007 11:49 pm
[1.34] Spontaneous Priority Reset |
I was adding a trigger state to one trigger that already had four, so I was adding it between state #3 and #4 to make it the new #4. Upon doing so, the editor appeared to rapidly switch between all current triggers. Once it finished, my entire GUI was rearranged. The priorities were changed. Is there any way to stop this from happening in the future? Thanks!
EDIT: It appears everything has started anew from a priority number in the 21,000s. There is nothing below. Ideas? |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Wed Jul 04, 2007 3:41 am |
I need more step-by-step instructions on how to reproduce this. Adding a new trigger state should always add the state to the end (so the new state should have already been state #4). So I'm not sure how you were trying to add it between 3 and 4. When you drag a trigger to a new position, CMUD will change the priorities of the triggers below it, but it shouldn't effect any triggers outside of the states of the current trigger.
Priority numbers for new triggers are always 10*Numtriggers where Numtriggers is the number of triggers that you have. This number continuously increases as you add new triggers, so old priority numbers never get reused within a package. If your priority number is in the 21,000s then somehow you have created over 2100 triggers in your package so far, which sounds a bit high. |
|
|
|
forren Novice
Joined: 26 Apr 2007 Posts: 44
|
Posted: Wed Jul 04, 2007 3:34 pm |
Okay, I just reproduced it again.
The trigger: ^You chew an arnica bud, then spread it on your (%w).$
State 1: (*) <--Within lines 1
State 2: ^The arnica bud has no discernable effect.$ <--- Reparse
State 3: ^(%d)h <---Reparse
State 4: ^<>-$ <--- Reparse
State 5: ^-$ <---- Reparse
State 6: * <---- Reparse
What I did was click on one of the states near the bottom (four or five) and go to New, Trigger State. It then caused the settings editor to rapidly pass through every setting. After it finished, my priorities were rearranged (GUI is out of order now). It allowed me to create a trigger state between the others without dragging-dropping. Not all the priorities were changed, but a lot seem to have been. |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Wed Jul 04, 2007 5:34 pm |
I cannot reproduce this with your instructions. I created the same trigger that you showed above in a new session and when I added the new trigger state between four and five, it worked fine here. It seems that there might be a problem somewhere else in your settings. You can email your *.pkg file to support@zuggsoft.com and tell me which trigger you are trying to edit and I'll try it with your settings.
|
|
|
|
NitroGlycerine Beginner
Joined: 26 Apr 2007 Posts: 29
|
Posted: Tue Aug 21, 2007 12:32 am |
Same thing happened to me.
Hard to describe the exact situation, but basicly all button priorities were all messed up all of a sudden when I added a new button state. The image of the button in the package editor seemed to quickly flash through all existing buttons. |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Tue Aug 21, 2007 1:20 am |
This is already fixed in v2.0
|
|
|
|
|
|