--- In [email protected], David Troesch <davidt.pproyg2...@...> wrote: > > > The latest exe I uploaded has a sleep delay just after the call to set the > > global flag in ppro.dll to disable hot keys; I don't know if that will help > > or not. > > The latest has gone backwards for the Macro functionality. It's back to > not sending the key at all till a window focus change to 32-bit window. > > > Note that I only added this delay macro key send; if it helps, I will added > > for keys command as well. > > > > > >> With the current .exe: > >> If the command is: > >> > >> *Keys abc`123 > >> *Keys `abc123 > >> *Keys abc123` > >> > >> it types fine > >> > >> If the command is: > >> *Keys ` > >> > >> then it has the delayed output. > > > > How very strange. PowerPro is doing nothing different in this case afaik. > > A couple things to test if you have some spare moments: > > > > keys `` > > keys `a > > keys a` > > keys {sinp}` > > I see there is no debug output at all to the debug.txt with this version. > > With Macro as hotkey: > > keys `` > -types ` into the notepad window, and the second ` is held just like if > it was by itself. > keys `a > -types `a completely into notepad. > keys a` > -types a into notepad, ` is held till window focus change. > keys {sinp}` > -same as if it was keys `
So it seems that if macro character ` is last key sent, it gets treated as hot key. This means that somehow, for 64 bit apps, the re-enabling of hot keys happens one character too soon. I don't understand why. I uploaded an exe with another delay at end of hot keys sending just before re-enabling; it also incorporates an way of disabling the hot keys which does not involve calling the dll. It seems we already have a viable workaround with Macro2, but if you have time I'd like to see if this one helps. Last try, I think. > They work fine, apparently someone forgot to tell the windows > programmers it's not supposed to work there, so they didn't break it :) I would guess that the hooks are still honored, but the dll is no longer mapped into the hooked process address space. That would mean that some features of PowerPro won't work, e.g. I believe the currentdir keyword relies on this.
