Hi David,
I don't remember having ever seen this behavior.
Are these global hotkeys, or specific to a particular window? One behavior
I have seen with reloading is when you have written your code for hotkeys
for a program-specific app, and so your hotkeys make reference to the
activeWindow object when being defined (because you can reasonably assume
activeWindow is the window associated with the program which caused your app
to start running).
What I did run into though was when restarting such an app, I would
sometimes be in the app manager when I restarted it, and so the activeWindow
object pointed to the app manager window, and my hotkeys would appear not to
be working in the program my app was designed for.
If they're global in nature, I can't think of any other guesses.
hth,
Chip
________________________________
From: David [mailto:eleph...@tele2.no]
Sent: Friday, March 23, 2012 10:30 AM
To: gw-scripting@gwmicro.com
Subject: Hotkeys and reloading an app
Throughout the development of an app, it is necessary to reload the
app quite frequently, whenever you have made changes to its code. I use to
have the app manager open, and then open the code itself in a Notepad
window. That way, I can alt-tab to the code, do my changes, alt-tab back to
the app manager, and press the Reload hotkey to have the app reloaded.
This works pretty fine. That is, for a few times. But every now and
then, without any good reason, my app is reloaded but none of the hotkeys
that my app is using, will work. If I for instance have defined the hotkey
of Alt-Shift-1 to perform a certain action in my app, this will work the
first few times I reload the app. Then, all the sudden, reloading the app,
alt-shift-1 ill do absolutely nothing. No matter how much I try to press the
hotkey, it does perform nothing. Reloading the app will not fix this problem
either. Only way I have found to get my hotkeys working again, is to end WE
(by Ctrl-Ins-F4, for instance), and then restart WE.
As developing an app could include numerous reloads in one day,
having to stop and restart WE several times, is quite anoying. Anyone has a
fix for this? The hotkey section of the app was designed by the Framwork
app, so should be properly coded. Then, why this drop out of hotkeys
functionality? Seems to me, as if something goes wrong in the clearing and
re-registering of the hotkeys, through the reload session. GW, could you
please look into this. Maybe a small delay, between the clearing of the
hotkeys from memory, before the actual reloading of the app. I don't of
course know, if this is where the problem is - but that is the only imediate
thing I can come up with, why the hotkeys do not re-register properly.
Anyone else seeing this behavior? Running WE7.5.3, under XP Pro all
up-to-date.
