![]() |
2011-10-29
, 11:52
|
Posts: 1,101 |
Thanked: 1,185 times |
Joined on Aug 2008
@ Spain
|
#172
|
Okay, so going back on my previous question...
I can finally get an F3 signal sent 100% of the time now if I have this in my script.
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
I don't understand why I have to force this so many times.
Besides that, it's a little laggy doing it this way.
Any possible clues or a different direction I can take here?
Kind regards.
xte 'keydown F3' /usr/share/snx/usleep 100000 xte 'keyup F3'
#!/bin/bash #your script stuff... xte 'keydown F3' sleep 0.1 xte 'keyup F3'
![]() |
2011-10-29
, 23:11
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#173
|
![]() |
2011-10-30
, 17:34
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#174
|
![]() |
2011-10-30
, 20:43
|
Posts: 1,101 |
Thanked: 1,185 times |
Joined on Aug 2008
@ Spain
|
#175
|
When I tap on either side of the screen, it will bring up the virtual keyboard.
How can I make it so that this only happens just once?
A double tap by accident will stack two of them on top of each other, still leaving one of them on the screen after the other one closes.
This is the script I'm using to launch it.
xkbd -geometry +65509+140 -k /media/mmc2/N800/Keyboards/scumm.xkbd & echo $! >/tmp/xkbd2.pid
Cheers.
if [ ! -e /tmp/xkbd2.pid]; then xkbd.... fi
The Following User Says Thank You to maacruz For This Useful Post: | ||
![]() |
2011-10-30
, 22:23
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#176
|
![]() |
2011-10-31
, 06:41
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#177
|
![]() |
2011-10-31
, 12:23
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#178
|
Instead of sending a stream of fast key pressings, try to send the keydown event, wait a bit, and then the keyup event. May be that works
Code:xte 'keydown F3' /usr/share/snx/usleep 100000 xte 'keyup F3'
xte 'keydown F3' 'usleep 100000' 'keyup F3'
![]() |
2011-10-31
, 22:34
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#179
|
xte 'keydown F3' 'usleep 100000' 'keyup F3
![]() |
2011-11-01
, 02:17
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#180
|
I can finally get an F3 signal sent 100% of the time now if I have this in my script.
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
xte 'keydown F3' 'keyup F3'
I don't understand why I have to force this so many times.
Besides that, it's a little laggy doing it this way.
Any possible clues or a different direction I can take here?
Kind regards.