pickel dude

[boriar]

Is it posible to define more that two touch zones with "pickel wait-for-hit"?
Whenever i try to define three or more pickel don't-wait-for-hit. I can fine any documentation or orientation for it.

[tshering]

From the description it seems you have to define exactly two touch zones.

Syntax: wait-for-hit x1 y1 width1 height1 x2 y2 width2 height2
return value: 1 for button 1, 2 for button 2

[boriar]

No, actually I have two zones but i need to define more an seems that use:
wait-for-hit x1 y1 width1 height1 x2 y2 width2 height2 x3 y3 width3 height3
don't work at all.

[tshering]

Originally Posted by boriar

No, actually I have two zones but i need to define more an seems that use:
wait-for-hit x1 y1 width1 height1 x2 y2 width2 height2 x3 y3 width3 height3
don't work at all.

That is exactly what I have suggested. "define exactly two touch zones" implies: You cannot define one, three, four, ...

[frostschutz]

it prints the touched (X,Y) though, so you could define an unreachable touch zone and then parse the output yourself

[boriar]

Originally Posted by tshering

That is exactly what I have suggested. "define exactly two touch zones" implies: You cannot define one, three, four, ...

Sorry, i misunderstood you

Originally Posted by frostschutz

it prints the touched (X,Y) though, so you could define an unreachable touch zone and then parse the output yourself

Where are they stored?
Which variables?

[boriar]

Originally Posted by boriar

Where are they stored?
Which variables?

Nobody knows how can i get X and Y?

[tshering]

Originally Posted by boriar

Nobody knows how can i get X and Y?

It is as Frostschutz said.

[root@(none) ~]# result=$(/usr/local/Kobo/pickel wait-for-hit 0 0 0 0 0 0 0 0)
[root@(none) ~]# echo $result
Screen: (1024, 758) (0, 758) w: 0, h: 0 (0, 758) w: 0, h: 0 (903, 394)

(903, 394) are the values you are interested in.

[boriar]

Originally Posted by tshering

It is as Frostschutz said.

[root@(none) ~]# result=$(/usr/local/Kobo/pickel wait-for-hit 0 0 0 0 0 0 0 0)
[root@(none) ~]# echo $result
Screen: (1024, 758) (0, 758) w: 0, h: 0 (0, 758) w: 0, h: 0 (903, 394)

(903, 394) are the values you are interested in.

Ah! I see. Thanks.

[frostschutz]

You should read the output continuously... pickel | while read line do parse coordinates

I haven't actually tried this myself, but it should work...

[spelufo]

Sort of related... I've made this script to listen for a certain sequence of taps and execute stuff when they happen. The dimentions are for the H2O. It needs to be run in the background.

#!/bin/sh

# +------+------+------+------+
# |      |      |      | (x,y)|
# | (3,0)| (2,0)| (1,0)| (0,0)|
# |      |      |      |      |
# +------+------+------+------+
# |      |      |      |      |
# | (3,1)| (2,1)| (1,1)| (0,1)|
# |      |      |      |      |
# +------+------+------+------+
# |      |      |      |      |
# | (3,2)| (2,2)| (1,2)| (0,2)|
# |      |      |      |      |
# +------+------+------+------+
# |      |      |      |      |
# | (3,3)| (2,3)| (1,3)| (0,3)|
# |      |      |      |      |
# +------+------+------+------+
# |      |      |      |      |
# | (3,4)| (2,4)| (1,4)| (0,4)|
# |      |      |      |      |
# +------+------+------+------+


quadhit()
{
	/usr/local/Kobo/pickel wait-for-hit $(( $1 * 1080 / 4)) $(( $2 * 1440 / 5 )) 270 288 0 0 0 0 &>/dev/null
}


listen=true
while $listen; do
	
	quadhit 0 4
	[ $? -eq 1 ] || continue

	start="$(date +'%s')"

	quadhit 1 4
	[ $? -eq 1 ] || continue
	[ $(( $(date +'%s') - $start )) -lt 3 ] || continue

	quadhit 2 4
	[ $? -eq 1 ] || continue
	[ $(( $(date +'%s') - $start )) -lt 3 ] || continue

	quadhit 3 4
	[ $? -eq 1 ] || continue
	[ $(( $(date +'%s') - $start )) -lt 3 ] || continue

	listen=false	

done

exec /mnt/onboard/.kobo/koreader/koreader.sh

Does it consume a lot of resources to have pickel wait-for-hit running a lot?

[frostschutz]

You could grab the screen dimensions [1080 1440] from 'fbset' then it might work for all readers. It's a nice idea and I would assume that it does not take many resources in regular usage. Might be different when you use the sketch pad and use the screen a lot...

[spelufo]

OK, it turns out the previous script was totally wrong. Pickels coordinates are weird. The arguments tp pickel are from the top-left corner on the screen. The output is (Y,X) with coordinates from the top-right corner of the screen. Also, if you pass 0 0 0 0 as one of the rectangles it will take that rectangle as the whole screen, which is why I use 0 0 1 1 for the rectangle I don't care about.

#!/bin/sh

[ $# -gt 0 ] || {
        echo 'Usage: tap-actiond.sh COMMAND'
        echo '  Wait for a sequence of taps on the touch screen and exec COMMAND when they occur.'
        exit 0
}

FB_MODE="$(fbset | grep '^mode' | cut -d \" -f 2)"
FB_MODE="${FB_MODE%-*}"
FB_W="${FB_MODE%x*}"
FB_H="${FB_MODE#*x}"

w=$(( $FB_W / 4))
h=$(( $FB_H / 5))

waithit() {
        coords="$(( $1 * $w )) $(( $2 * $h )) $w $h"
        /usr/local/Kobo/pickel wait-for-hit $coords 0 0 1 1 &>/dev/null
}

listen=true
while $listen; do
        
        waithit 3 4
        [ $? -eq 1 ] || continue
        start=$(date +'%s')

        waithit 2 4
        [ $? -eq 1 ] || continue
        [ $(( $(date +'%s') - $start )) -lt 3 ] || continue

        waithit 1 4
        [ $? -eq 1 ] || continue
        [ $(( $(date +'%s') - $start )) -lt 3 ] || continue

        waithit 0 4
        [ $? -eq 1 ] || continue
        [ $(( $(date +'%s') - $start )) -lt 3 ] || continue

        listen=false    

done

exec $@

[spelufo]

It works from the shell via telnet, but not when I run it on boot. I don't know what is going on.

[frostschutz]

How do you run it on boot? udev kills scripts that take too long, you have to setsid...

Also I'm not sure about wait for touch, but pickel showpic required additional environment variables in some firmware versions. You can steal them from nickel's environment.