Zugg Software :: View topic

Apprentice Joined: 13 Feb 2004 Posts: 157 Location: USA

My button bar is in a class folder named ButtonBar. I have in it three gauges which have worked fine for ages.

Reorganizing my class folders a bit for tidiness, I moved the ButtonBar folder under a newly-created UI folder that also contains a speed menu folder, a macros folder, etc. Everything else continues to work; my button bar buttons all do what they ought, display properly, etc. I can still right-click them to jump to them in the settings editor.

But the gauges do not automatically update. If I open the settings editor to look at them, every time I click another tab they update at that moment. I've tried changing settings, even deleting and recreating them, and nothing helps. I also tried moving the folder back to its former location. But whatever I do, the gauge doesn't update except at the moments when I click tabs on its settings page.

The variables *are* updating, by the way. And the gauges are set to display changes. (Turning that off and back on doesn't help either.)

Is this a known problem with a workaround, or something I need to bug report, or something I'm doing wrong?

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

Delete the variables and let your triggers recreate them, then move them to whereever they need to be.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I think I have seen buttons misbehave before. My best suggestion is to export the class containing them to a text file. Then edit the text file to change all the button numbers to high numbers, remove/rename any IDs you have set, and set the caption portion of the #BUTTONs arguements to be in "" instead of {}. Then backup your .mud. Finally import the text file, then delete the old buttons. Doing things in this order should assure that new buttons are created and zMud knows which variables it has to pay attention to for updating things.

I am pretty sure zMud doesn't update everything on a change to any variable. I think it keeps a table that is used to quickly determine what needs updating. Evidently when you moved the buttons around this table got messed up. If the above steps don't clear it up go for a full export and fresh import.

Apprentice Joined: 13 Feb 2004 Posts: 157 Location: USA

Oddly, the problem healed itself overnight for no particular reason, so I won't get to figure out which of these kluges might have fixed it. But maybe if it happens again, I will. :)