WowAce

What steps will reproduce the problem?

1. Head into ZOMGBuff's options, Display section.

2. Click the Class Icon checkbox to enable it. The mouseover ZOMGBuffs button icon switches its icon to a class-specific one, as expected.

3. Try to click the option again to reenable the default icon.

4. Next, check and uncheck the Enable checkbox just above that.

What is the expected output? What do you see instead?

Expected: the original, default icon to appear again when you uncheck Class Icon. And the entire icon button to go away when unchecking Enable.

Instead: the Class Icon option "locks" & becomes disabled so that you can no longer checkmark it on or off. Clicking the checkbox further does nothing (no checkmark appears or goes away). The button remains with the class specific icon permanently.

And the Enable option does nothing at all. The checkmark both appears and goes away when clicking it unlike the above option. But nothing else happens; the icon button does not go away/come back as expected.

What version of the product are you using?

r187 loaded with no prior saved variables, WoW 4.0.3a live, USEnglish client/server.

Do you have an error log of what happened?

No errors.

Please provide any additional information below.

Ticket 169 is priority #1. But once the mechanics are working properly, these options are something else to fix.

These two buggy behaviors are 100% repeatable with the latest r203 (installed & tested with no prior saved variables).

Head into the global saved variables, delete the ["class icon"] = true, line (or set it to false) and the icon type properly returns to its default type on the next log on. But the options panel Class Icon problem still remains; its unable to return the icon to the default one after checkmarking it to get the class one.

As well, the Enable checkbox still does nothing at all; the icon remains showing at all times (did not change the saved variables as I want the icon showing).

Hope these problems can be fixed sometime.

P.S: nice job on resolving the AceTimer issue with r203; am back to using this again. The above bugs are still annoying, though.