I noticed this behavior in MushClient 4.84. I noticed it in my main copy as well as a fresh client that I downloaded (for convenience) from Aardwolf.com. I run Windows 7 Professional edition 64bit (8GB RAM, System drive has 40GB free, if it matters).
The dialog in question is accessed by following the menu Game->Configuration->Keypad...
The option in question is accessing the CTRL-modified macros by checking the box "Show Contents if CTRL Held Down".
What I noticed is that if I check that box and then click through to another configuration screen using the list on the left hand side of the configuration window (specifically, I tested is using "Aliases" and "Commands") I lose the ability to modify my CTRL-modified keypad macros. At that point, if I return to the "Keypad" configuration dialog, the checkbox is still checked but I'm viewing the unmodified macros. I can check/uncheck the box and it does not react like I would expect (by showing me my secondary macros for the keypad).
I can exit the dialog and reenter and this unexpected behavior continues. I can also exit and reopen MUSHClient. In fact (I had some other software to update), I can restart my machine and this behavior continues.
In a way, even the unreliability is unreliable. When attempting to recreate this from a fresh zip (downloaded from Aardwolf.com), it wasn't QUITE this destructive the first time. I was able to recreate the behavior, but when I closed and opened MUSHClient (the first time using this fresh copy) I was granted access to a working dialog again. However, when I attempted to recreate the issue a second time on that fresh copy, the unexpected behavior once again survived opening and closing the program. (After further testing, I think I "cancel"ed out of the configuration dialog and did not allow MUSHClient to save internal variables when closing it to notice this)
Specifically, I can recreate this issue through these actions:
* Download the zip available on Aardwolf.com
* Unzip that zipped file to some random folder
* Check and set permissions on that random folder to make sure my user has read/write/execute permissions
* Run Mushclient.exe
* (Click no to the automatic upgrades)
* Follow the menu path Game->Configuration->Keypad...
* Check the checkbox "Show Contents of CTRL Held Down" (notice that the macros all change to blank boxes because we haven't set any CTRL-modified macros yet)
* Check that checkbox two more times to verify that I'm getting the behavior that I think is correct (swapping between the default macros and the blank CTRL-modified set)
* WITH that checkbox checked, click on "aliases" in the list to the left
* Click on "Keypad" again
* Check/uncheck that checkbox. Notice that we now get no response
* Click on "OK" at the bottom of the configuration dialog and close MUSHClient
* Open it again and repeat; notice that you no longer get the expected response when checking that checkbox
The dialog in question is accessed by following the menu Game->Configuration->Keypad...
The option in question is accessing the CTRL-modified macros by checking the box "Show Contents if CTRL Held Down".
What I noticed is that if I check that box and then click through to another configuration screen using the list on the left hand side of the configuration window (specifically, I tested is using "Aliases" and "Commands") I lose the ability to modify my CTRL-modified keypad macros. At that point, if I return to the "Keypad" configuration dialog, the checkbox is still checked but I'm viewing the unmodified macros. I can check/uncheck the box and it does not react like I would expect (by showing me my secondary macros for the keypad).
I can exit the dialog and reenter and this unexpected behavior continues. I can also exit and reopen MUSHClient. In fact (I had some other software to update), I can restart my machine and this behavior continues.
In a way, even the unreliability is unreliable. When attempting to recreate this from a fresh zip (downloaded from Aardwolf.com), it wasn't QUITE this destructive the first time. I was able to recreate the behavior, but when I closed and opened MUSHClient (the first time using this fresh copy) I was granted access to a working dialog again. However, when I attempted to recreate the issue a second time on that fresh copy, the unexpected behavior once again survived opening and closing the program. (After further testing, I think I "cancel"ed out of the configuration dialog and did not allow MUSHClient to save internal variables when closing it to notice this)
Specifically, I can recreate this issue through these actions:
* Download the zip available on Aardwolf.com
* Unzip that zipped file to some random folder
* Check and set permissions on that random folder to make sure my user has read/write/execute permissions
* Run Mushclient.exe
* (Click no to the automatic upgrades)
* Follow the menu path Game->Configuration->Keypad...
* Check the checkbox "Show Contents of CTRL Held Down" (notice that the macros all change to blank boxes because we haven't set any CTRL-modified macros yet)
* Check that checkbox two more times to verify that I'm getting the behavior that I think is correct (swapping between the default macros and the blank CTRL-modified set)
* WITH that checkbox checked, click on "aliases" in the list to the left
* Click on "Keypad" again
* Check/uncheck that checkbox. Notice that we now get no response
* Click on "OK" at the bottom of the configuration dialog and close MUSHClient
* Open it again and repeat; notice that you no longer get the expected response when checking that checkbox