| Maxdamantus | Hmm .. wonder if there's a shortcut to open the hildon-status-menu dialogue.. my digitiser seems to have gotten worse. | 12:55 |
|---|---|---|
| Maxdamantus | (or some dbus command that I can bind to a key combination) | 12:58 |
| KotCzarny | you can try xdo + location click | 13:01 |
| Maxdamantus | Heh. | 13:02 |
| KotCzarny | or xdotool | 13:02 |
| KotCzarny | and you can always hack the hildon source to add a shortcut | 13:03 |
| Maxdamantus | Seems that you can detect key presses specifically in the task switcher, with "/apps/osso/hildon-desktop/key-actions/dbus_launcher_navigator", which would be a convenient place to put the shortcut, but probably need some way other than xdo to open the menu from there. | 13:06 |
| KotCzarny | you can use xdotool to 'click' in 0,0 | 13:07 |
| Maxdamantus | 0,0 will open the task switcher, which already has a keyboard shortcut (ctrl-escape; I already use that a lot) | 13:08 |
| KotCzarny | hmm | 13:08 |
| KotCzarny | what is hildon status menu then | 13:09 |
| Maxdamantus | and in the task switcher you can't directly open the status menu dialogue. | 13:09 |
| Maxdamantus | The dialogue with network connection, volume, etc. | 13:09 |
| Maxdamantus | er, ctrl-backspace* | 13:10 |
| bencoh | what if you click on, say, 5,5 ? | 13:11 |
| bencoh | or some other coordinate | 13:11 |
| bencoh | ah, not 5,5, nevermind | 13:11 |
| bencoh | basically the status-menu button coordinates, not sure what those would be | 13:11 |
| KotCzarny | i still dont know what is hildon status menu, must be rusty memory | 13:12 |
| KotCzarny | because status panel applets all have specific coords then | 13:12 |
| bencoh | KotCzarny: the thing with the clock and various status applet | 13:12 |
| KotCzarny | i must find my n900 and check | 13:12 |
| bencoh | KotCzarny: | 13:13 |
| bencoh | https://tabletui.files.wordpress.com/2009/12/14.png | 13:13 |
| KotCzarny | then yeah, most likely 240,0 click | 13:14 |
| bencoh | depends on the theme actually | 13:14 |
| KotCzarny | or 64,0 | 13:14 |
| bencoh | (I think) | 13:15 |
| KotCzarny | still, still would need additional clicks to do anything with it | 13:15 |
| KotCzarny | xorg had mouse-emulation mode | 13:16 |
| KotCzarny | maybe it's not completely disabled in maemo | 13:16 |
| Maxdamantus | I've been wanting to experiment with mouse emulation using the touchscreen. | 13:19 |
| Maxdamantus | Wonder if there's something you can just tell to Xorg to make that happen. | 13:20 |
| Maxdamantus | (ie, basically use the touchscreen as a relative positioned device rather than absolute) | 13:20 |
| KotCzarny | as in 'gamepad overlay' type of thingy? ;) | 13:20 |
| Maxdamantus | No, as in just pretend it's a touchpad. | 13:21 |
| Maxdamantus | like on a laptop. | 13:21 |
| Maxdamantus | So you just have a regular mouse and you move the position of the mouse relatively. | 13:21 |
| KotCzarny | MatchIsTouchpad "on" | 13:23 |
| KotCzarny | Driver "evdev" | 13:23 |
| KotCzarny | Option "Mode" "absolute" | 13:23 |
| KotCzarny | but it might be set up differently on 2009's xorg | 13:24 |
| KotCzarny | is xinput available on maemo? | 13:25 |
| KotCzarny | xinput set-mode ABSOLUTE|RELATIVE | 13:26 |
| bencoh | I don't think it is, but adding it shouldn't be too hard | 13:43 |
| Maxdamantus | xinput 1.6 or whatever I was trying to build is too recent for some of the packages in maemo, will try building an older version tomorrow. I have a feeling I've actually already tried just setting the mode to relative but it didn't work. | 13:47 |
| Maxdamantus | Will try on my laptop at work tomorrow, since that has a touchscreen. | 13:47 |
| KotCzarny | maybe the driver code for touchscreen has some param | 13:47 |
| KotCzarny | ie. kernel module option | 13:48 |
| KotCzarny | which interface touchscreen uses in x for maemo? | 13:48 |
| Maxdamantus | interface? it's just using evdev. | 13:49 |
| KotCzarny | evdev is and interface | 13:49 |
| KotCzarny | then maybe those options i've pasted earlier could work | 13:49 |
| KotCzarny | replacing absolute with relative or whatever is supported | 13:50 |
| KotCzarny | but it would also need enabling mouse pointer | 13:50 |
| KotCzarny | and disabling autoclicking on press | 13:50 |
| Maxdamantus | Right, so that's probably why you can't just set the mode. | 13:54 |
| KotCzarny | some tap to click should be in touchscreen driver | 13:57 |
| Maxdamantus | Sounds like that mode indeed isn't for controlling how the input driver is meant to handle the input but for setting some flag in events sent to clients. | 13:57 |
| Maxdamantus | so when an X client receives a "mouse" event, it just has a flag that says whether it was from an "absolute" device or from a "relative" device. | 13:57 |
| KotCzarny | still a nice idea to make, and game emu folks would love it 10 years ago | 13:58 |
| KotCzarny | :) | 13:58 |
| Maxdamantus | I think I saw in a video that Pinephone was doing it. | 13:58 |
| KotCzarny | pinephone use recent software | 13:59 |
| KotCzarny | so it's easier to pull off | 13:59 |
| KotCzarny | *uses | 14:19 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
