--- In [email protected], Gerhard Fiedler <[EMAIL PROTECTED]> wrote:
> On 8/7/05 14:45:38, in gmane.comp.windows.power-pro you wrote:
>
> >>> Replace SendKeys("^x") with Keys ^x
> >>
> >> Works! (That is, sends ^x.) Thanks a lot. However, I also tried
to use
> >> "Message VSCut" (no quotes), and no message box came up. What did
I do
> >> wrong?
> >
> > It could be a focus problem. Try
> > Message VSCut *takefocus
>
> Rats... I know I said above that it worked, and I'm pretty sure that
it did
> work. But now it doesn't... neither the Keys command, nor the Message
> command with *takefocus. Here are the two lines I have now in my ini
file:
>
> VS.Cut=20,0,0,45,81,1,,,Keys ^x,1,1,0,1,0,0,,,,,,ViewSonic special key
> VS.Copy=20,0,0,46,74,3,,,Keys ^c,1,1,0,1,0,0,,,,,,ViewSonic special key
There may be a timing issue, or you may have to use KeyTrap.SendKeys()
or use {fast}, or both, or you may have to specify the caption or ...
For example,
KeyTrap.SendKeys(?"{fast}{to ^+*}^x")
> I'm pretty sure they get triggered, because they eat their
associated key.
> If I set the configuration for them not to eat the key, the key comes
> through. I guess this makes it pretty safe to assume that
> - keytrap is loaded,
> - keytrap uses this ini file,
> - the reloading of the ini file works (because I can toggle the "eat
key"
> option and it behaves just like it should WRT that)
> - the respective entry gets triggered.
>
> But the command doesn't result in anything I could see.
>
>
> >> And it still doesn't "eat" the CapsLock key. After more reading,
I think
> >> I may have to write a script that gets called when the CapsLock key
> >> gets pressed, and that then uses keytrap functions to perform
functions
> >> and eat key strokes etc. as required. Is this the only way to get rid
> >> of the CapsLock activation?
> >
> > It's in the To-Do list, read the readme file.
>
> Ah -- I missed that part when I read the file, due to a lack of a
general
> understanding of the features at that point.
>
> > However, I'm now wondering if it might not possible unless completely
> > disabling/blocking the key...
>
> Don't you think that the functionality you outline would be possible to
> even do in a script, using keytrap commands? Can keytrap trigger a
script
> on CapsLock.down, which then waits until either one of the associated
> action keys gets pressed and released, or CapsLock gets released?
Something
> like this:
>
> (keytrap config)
> on CapsLock.down execute script and eat CapsLock.down
>
> (script)
> on any keyevent:
> if CapsLock.up: send CapsLock.down then CapsLock.up
> if Q.down: send ^x
>
> This would still leave a CapsLock.up and Q.up event go through in
the case
> of a CapsLock-Q (like my keyboard generates), but I hope that this would
> not cause any strange actions. If it does, this could maybe be handled,
> too.
Yes, it's possible. But, the problem here is that there could be a
significant delay between the actual keystrokes and key-records,
especially for a fast type writers.
Sean
------------------------ Yahoo! Groups Sponsor --------------------~-->
<font face=arial size=-1><a
href="http://us.ard.yahoo.com/SIG=12hmg9puo/M=362131.6882499.7825260.1510227/D=groups/S=1706030409:TM/Y=YAHOO/EXP=1123467797/A=2889191/R=0/SIG=10r90krvo/*http://www.thebeehive.org
">Get Bzzzy! (real tools to help you find a job) Welcome to the Sweet Life
- brought to you by One Economy</a>.</font>
--------------------------------------------------------------------~->
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/
