This dosn't work, but crudely tries to demonstrate the idea. Maybe someone smarter knows the trick?
It's a great idea, and the code works perfectly for me on WinXP. I don't feel like rebooting to linux, so I won't try it now. What do you mean by "doesn't (sic) work"? | [reply] |
"What do you mean by "doesn't (sic) work"?Well I think the OP wanted to turn a key into a switch which is on as long as it is held down, and is off when it is released. The code I posted will still "repeat" on linux, ( I hav'nt tried it on Windows). That is if you hold the key down, you will get a succession of "pressed-released events". If the OP had a binding to 'release' , then he would be repeatedly starting-stopping.
Just for fun, and because I think this could be useful in my "bag-o-tricks", I tried a few more things, but was still unsuccessful. For example:
#!/usr/bin/perl
use warnings;
use strict;
use Tk;
my $mw = MainWindow->new;
$mw->bind("<Key>", sub { &pressed } );
$mw->bind("<KeyRelease>", sub { &released } );
MainLoop;
sub pressed{
print 'Key: ', ${Ev('K')}, " pressed\n";
$mw->bind("<Key>", sub { } );
$mw->bind("<KeyRelease>", sub { } );
}
sub released{
print 'Key: ', ${Ev('K')}, " released\n";
}
This code above will break the "auto-repeat" of the X-windows,
but I can't seem to find a way to "re-enable the key bindings" when the key is actually released. I tried adding timers, which watch the output, expecting a succession of "pressed" events, and if the output stops, then call the "stop_function".For example:
#!/usr/bin/perl
use warnings;
use strict;
use Tk;
my $mw = MainWindow->new;
$mw->bind("<Key>", sub { &pressed } );
MainLoop;
sub pressed{
print 'Key: ', ${Ev('K')}, " pressed\n";
$mw->bind("<Key>", sub { } );
$mw->bind("<KeyRelease>", sub {&pressed } );
}
This will just print a succession of "pressed" as long as the key is held down, and will stop when the key is released. So I thought about opening a FH to \$tempvar, and writing the output to it, then have a timer, truncate FH after a time period.
If the length($tempvar) == 0, then I know the key was released, and can call the stop_function. But the timers eluded me, because either I spawned multiple timers, or the timing of the timers was funky, and unusable. But as of now I
think this is the only method that will work, but it depends on what the "internal repeat key rate" is on your system. So after all that, I figure, it would be better to take a different approach, like have 1 key to initiate, and a differently named key to stop.
(Which is normally how it's done).
I'm not really a human, but I play one on earth.
flash japh
| [reply]
[d/l]
[select] |
Right now I have it set up where one key activates and another stops, and I guess I'll have to stick with that. I really thought this was some easy problem that I could easily find a fix for, but I guess not. Thanks, for the effort though. If I dream up anything magical, I'll let you guys know.
As for my system, I'm on a school lab machine, so I don't know all of the specifics. Also, I'm normally an XP user and this is a linux/xwindows. I'm looking at a standard Dell package deal if that helps at all with type of keyboard and whatnot.
Anyway, thanks again.
-kfm-
| [reply] |