Zugg Software :: View topic

Apprentice Joined: 06 Apr 2004 Posts: 173

When you create a new trigger, and only have it partially filled in (bugs as a result of not having all the variables decrared) and then click on the new variable button, leaving the trigger section. It wont save the stuff you've created in the trigger when you leave it for the new variable creation box. When you go back to your trigger it will be either gone, or be back at a former state. Is there any way of fixing this? I'm modyifing a lot of stuff all at the same time... and have to re-enter it all every time I create a variable.

Posted: Sat May 19, 2007 1:13 pm

I couldn't get this to fail. Please post exact steps to recreate the bug. Here's what I did:

1) Open CMUD, close the sessions window, open the package editor from the Settings button.
2) Click New... Trigger. Give it a pattern (test) and a body (a few "test"s repeated).
3) Without clicking save, click New... Variable. Give the variable a name.
4) Click back to the trigger. The text I entered is still there.
5) Enter some more "test"s and repeat steps 3 and 4. Still no change.

Posted: Sat May 19, 2007 9:24 pm

Fang your example won't work because this you don't have invalid syntax.

I have noticed that behavior and I believe it was even discussed in another thread. I think it has to do with the new syntax editor or parser, but you'd need to an explicit save in those situations to prevent from accidentally saving bad code.

At any I think this is the way it should be... but I'm a big fan of the save button. (I once lost my code repository at work and we had to use my local backups to recreate it.)

Also I'm not sure why you'd get a syntax error if a variable isn't define. It get's highlight differently but to my knowledge (and based on what I've seen) there isn't a syntax error. Can you post an example of code that has syntax errors when the variable isn't defined?

Apprentice Joined: 06 Apr 2004 Posts: 173

no it doesn't output "Syntax error" it just highlights differently as Tech said. But I think of that as a syntax error... Sorry for the confusion. I'll see if I can post an exact rundown of how to get it to not save.

Apprentice Joined: 06 Apr 2004 Posts: 173

Actually you dont even need to have errors in it,
1)just open up the editor
2)click the trigger button on the left panel
3) then click new up at the top
4) fill in a pattern)
5) fill in any command)
6) click on variable, or alias
7) click new again, and poof! it's gone at that point.

what would be nice is if...
1) if you want to KEEP this behavior, then when you navigate away, put up a dialog box asking if you want to save the changes.
2) autosave like was done in zmud

Apprentice Joined: 06 Apr 2004 Posts: 173

I didn't select new>alias
I selected the alias icon or the variable icon on the left panel. so the views of the database actually get changed before I create a new alias, or new variable. When I click on the trigger icon again the trigger wont be in the list of created triggers.

Posted: Sat May 19, 2007 11:09 pm

Confirmed. Even easier to reproduce:

1) Open the editor
2) Edit a new or existing setting, but don't click save
3) Change the filter type using the bar on the left. Even changing from All to the type of setting you selected will work. Changes have vanished.

Posted: Mon May 21, 2007 5:16 pm

Confirmed and added to bug list. The problem is with clicking the filter buttons on the left. You don't need to click the Alias filter button to create a new alias. Just select "Alias" from the New pulldown menu in the toolbar. This is the way you are supposed to create new items.

Clicking one of the filter buttons causes the actual database display to be filtered, and it looks like there is a problem with the database saving in this situation. I'm calling the database "Post" routine before changing the database filter, but that doesn't seem to work for some reason. Anyway, it's on the bug list, but try to get used to using the New pulldown menu for now.