This is really nice ....
follow this active window : what appears if the mouse is moved to the upper right corner (calling KeyTrap.ResetKeys) : key that would do the same function poptray : help dialog : F1 notepad2 : right context menu : right mouse button firefox : right context menu : RMB (not consistently) taskbar : right context menu : RMB desktop : right context menu : RMB internet explorer : RCM : RMB quicktime : File dropdown : alt F realplayer : help dialog : F1 what is going on ??? can't program to activate a KeyTrap.ResetKeys? --- In [email protected], "drmwpdc" <[EMAIL PROTECTED]> wrote: > > Sending a KeyTrap.ResetKeys with hotkey calls that are already > programmed to do a function does strange things - windows appear that > are not called ie. help dialogs, right contextual menu etc. > > Most likely a KeyTrap.ResetKeys needs to be sent by itself. > Configured sending the mouse to the upper right corner of the screen > to call KeyTrap.ResetKeys. > > Quick flick of the mouse and my keys are back (time will tell). > > > --- In [email protected], "drmwpdc" <[EMAIL PROTECTED]> wrote: > > > > I had another keytrap failure - this time code 255 came back. > > > > This has no rhyme or reason. > > > > > > I reverted back to what I thought was a safe version of powerpro and > > the error occurred again, code 32. > > > > All I'm going to do is add an addition function to my hotkeys (one > > that I frequently use) and have it do a KeyTrap.ResetKeys along with > > it's function (unless excessive KeyTrap.ResetKeys calls is > > contraindicated) > > > > it's a fix, not proper, but functional > > > > > > > > --- In [email protected], "swzoh" <[EMAIL PROTECTED]> wrote: > > > > > > --- In [email protected], "drmwpdc" <[EMAIL PROTECTED]> wrote: > > > > > > > > Using the win.debug(KeyTrap.GetPressedKeys) > > > > The first time I got a code 32 (space), and after I pressed the > > space > > > > bar, I recieved no codes and the keytrap worked. > > > > > > > > The second occurance, I got a code 32,234 (space and an OEM > > specific > > > > key), pressed the space and then only got the 234 reported back. > > > > > > > > Did the (KeyTrap.ResetKeys) and the 234 was released and keytrap > > > > worked. > > > > > > > > I have no keys configured using powerpro or keytrap that would > > monitor > > > > or send a (space) key (if that is any assistance to you). > > > > > > > > > > I suppose 234 OEM key is similar in nature to IME keys, i.e., they > > > send only "KEYDOWN" message, without accompanying "KEYUP" message > > when > > > releasing the keys. Then it's understandable that the key remains > > > pressed once after pressed. The problem in your case seems, > however, > > > that this key's got pressed without your pressing the key. Is it > > right? > > > > > > BTW, I have no idea why the SPACE key remains pressed in your > > machine. > > > But, I recall that DEL key used to remain pressed in my system > > after I > > > call Task Manager by pressing Ctrl+Alt+Del. > > > Do you have any hotkey using space, or are you using frequently > > > Alt+Space hotkey which call system menu? > > > > > > Anyway, you can avoid the problem by adding the following section > to > > > your keytrap/mousetrap ini files: > > > > > > [IgnoreVKCodes] > > > OEM=234 > > > SPACE=32 Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
