ok, ok you won (wow)
but....
I never wrote that code connected to control can switch state of control, look at it:
Quote:
|
hmmm, buttons maybe disabled via calling enablewindow (you can patch rigth part of code) or via resources (you can find and correct res part of exe), but it is possible that code for button is not connected to button (maybe it is not in exe at all ) and here can be problem pointed by LOUZEW
|
and what was significance of my post? point to alternative that control can be disabled by programmer in resource editor (if I remember right there was a version of rslogix which had disabled controls in resource editor) and that simply enabling control must not automatically lead to right functioning of control.
eg
a time ago I saw program in which developer done this (I guess)
1) disable menuitems and buttons for saving and printing
2) in message loop for IDSAVE and IDPRINT do only return
but code for saving and printing was still here ...
well it was not so hard to find code for saving and printing in IDA and make some jumps at right places, but situation was as I wrote control disabled by res editor (so spying on EnableWindow lead towards nothing) and code was disconnected from control so there was a need to do some RI works on it
this and ONLY this was sense of my post
regards