Zugg Software :: View topic - [1.32] Same issue from [1.29] #RESET and UI made variables not resetting.

Beginner Joined: 20 Mar 2007 Posts: 27

anyone else having issues with variables not resetting to thier default values?

Even after #RESET I had a few fail to reset.

Also, I even had one not reset after logging out.

I'll try to post examples if i find them.

Edited/Update: I am still having trouble with variables made with the UI. I have deleted them then tried remaking them. Don't know what to post from my code. I can email the package I use. The variables are not resetting even after closing the program. This is quite the hinderance with scripting. Any more thoughts on this issue??

Posted: Tue Apr 24, 2007 11:49 pm

Seems to depend on whether or not you use the UI to create the variable. Ran this code:

#var test sdsdsdsdss lol
#show @test
#reset
#show @test

and it worked. Created the variable manually (and checked "Use Default") and the second #show showed the original value.

EDIT: Though I deleted and recreated the variable with the UI and now it's working.

Posted: Wed Apr 25, 2007 3:08 am

Hmm, so are you saying it only fails the first time a variable is created in the UI?

Beginner Joined: 20 Mar 2007 Posts: 27

I know I have created a variable through the UI Package Editer and even today when I logged on to my MUD and even used #RESET it is still no reseting.

Going to delete it.

Remade it on the command line. Then moved it to the correct module. Tried #RESET still will not got back to the orginal value.

Closed the progam, had am error, sent that. Then it create the variable back in the main window. (Main window has no setting and everything is in a module)

Deleted it and recreated AGAIN with the UI. AGAIN the program crashed, sent that too.

Variable was still in the module window, BUT was NOT the default value.

Any suggestions?

Posted: Wed Apr 25, 2007 3:00 pm

It seemed that way the first time, Zugg, but then I created another variable with the UI to try again and it worked. Could be that I made a mistake the first time. I can't get it to do it again.

Beginner Joined: 20 Mar 2007 Posts: 27

Bumping this up to readdress this issue if possible, see edited first post.

Posted: Mon May 07, 2007 5:52 pm

You can send me your *.pkg file as an email attachment to the sales@zuggsoft.com account.

Posted: Tue May 08, 2007 12:37 am

Well, I found the problem. Your Mobile-Main package only contains a Module (no Window). So, when you load it for a session, you end up with the main session window as Untitled. The #RESET command only resets the variables within the current window. It does *not* reset variables or triggers in other packages.

I am improving the #RESET command so that in addition to being able to specify a certain class to reset, you can also specify a specific Module to reset. Then, you can do:

#RESET "Mobile Main"

to reset the variables in your module.

In playing with this, I also had the idea of creating an alias within your MobileMain module called "resetmain" that would use the #RESET command. However, it seems that the alias gets run within the context of the current window, so this still doesn't work.

So, I am also going to change the #RESET command so that it uses the current context (of the alias containing it) rather than using the current window with keyboard focus.

Posted: Tue May 08, 2007 12:44 am

Btw, is there a reason that all of your buttons seem to be gauges? You have several gauges that do not have any variables set for their current/max values. For example, your "General Defense" button on the right is set as a gauge even though it doesn't have any variables associated with it. Seems weird that you aren't just using normal buttons.

Beginner Joined: 20 Mar 2007 Posts: 27

In Zmud, gagues where easier to set graphic with and having a "custom" layout with buttons with BMP was easier using gagues versus "push" or other buttons. Guess that just stuck with me to use guages as all buttons pretty much. Does that affect anything?

Any thing I can do until #RESET is changed??

Thanks Zugg!!!

Posted: Tue May 08, 2007 2:15 am

Go ahead and download v1.33 for the #RESET fix.

Gauges will update slower than buttons. And a regular button should still work with images and colors. In fact, a gauge is implemented as a button in CMUD except that the background of the button is drawn as a two-color gauge value. But everything else is the same. So if you just want icons and a single background color, a button will work just as well as a gauge and will be faster in drawing/updating. You should just be able to change your non-gauge buttons to "Push" buttons without any trouble.