 |
Arminas
Wizard
Joined: 11 Jul 2002
Posts: 1265
Location: USA
|
 Posted: Fri Feb 02, 2007 6:42 pm
[1.24] %btnenable #T- #T+ Bugs
|
If you use the button priority number with %btnenable you are able to consistently enable or disable a button irregardless of if there is a class of the same name or ID.
%btnenable will disable a button using the button ID or the button Name.
%btnenable will NOT enable a button using the button ID or the button Name.
#T- Name Will disable a button using the button name if there is NOT a class of the same name.
#T- Name button Will disable a button if there is NOT a class of the same name. It disables the class instead.
#T- ID button Will NOT disable a button if there is a class with a name matching the ID. It disables the class instead.
#T+ Has the same issues above with of course enabling instead of disabling.
With #T basically the optional TYPE is being ignored |
|
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Feb 05, 2007 8:35 pm
|
The %btnenable is already reported and on the bug list. I've added the new issue with #T- and #T+ not using the optional TYPE argument to the bug list.
|
|
|
|
|
|
|
|
