WoW:API CheckButton SetChecked: Difference between revisions

m
Remove singature made using ~ in main namespace
m (Remove singature made using ~ in main namespace)
Line 42: Line 42:
In patch 1.11 it seems like this method was changed so that it no longer works when passing '''nil''' as argument. I have tested that it works as intended when passing '''true''' and '''false'''.
In patch 1.11 it seems like this method was changed so that it no longer works when passing '''nil''' as argument. I have tested that it works as intended when passing '''true''' and '''false'''.


That's not really correct. Passing "nil" will still uncheck the button, but passing *no* argument (although it should end up being nil for LUA) will enable it, also passing a table ({...}) will now check the button. [[User:Watchout|watchout]] 12:43, 29 June 2006 (EDT)
That's not really correct. Passing "nil" will still uncheck the button, but passing *no* argument (although it should end up being nil for LUA) will enable it, also passing a table ({...}) will now check the button.


Yep, you're right watchout.  Also, I think this behavior was changed in 1.11.1, as it was fine right after 1.11. [[Krellmax]] 14:34, 29 June 2006 (MDT)
Yep, you're right watchout.  Also, I think this behavior was changed in 1.11.1, as it was fine right after 1.11. [[Krellmax]] 14:34, 29 June 2006 (MDT)
Anonymous user