| Wizzup | looks like my chimaera report about autoscan and wpasup is wrong | 01:24 |
|---|---|---|
| Wizzup | I think I have some weird local config | 01:24 |
| Wizzup | yup | 01:30 |
| sicelo | mmm, i got a phone call (droid 4) ... and now lost touch | 08:55 |
| sicelo | ah, at least locking via power key and unlocking restored it | 08:55 |
| Wizzup | sicelo: yes, this I see sometimes too, it seems mce related | 09:14 |
| Wizzup | because I checked that on kernel the ts does still respond | 09:14 |
| Wizzup | at least iirc | 09:14 |
| Wizzup | on kernel level | 09:14 |
| freemangordon | Wizzup: playing with gtk3/him.... | 10:19 |
| freemangordon | I am not sure gtk IM contexts were ever designed for VKB | 10:19 |
| freemangordon | maybe I am missing something, but I see no clear event/criteria when to show or hide the vkb | 10:20 |
| freemangordon | in gtk2, show/hide virtual functions were added by Nokia | 10:20 |
| freemangordon | there is filter_keypress, but that does not really help much | 10:24 |
| freemangordon | for exmaple, chromium generates focus in / focus out events only | 10:34 |
| freemangordon | *example | 10:34 |
| freemangordon | I don;t want to patch gtk3, but... | 10:37 |
| freemangordon | uvos: how did you test atspi? more specifically - the part that you have to re-enter an edit field to get an event. did you use chromium to test? | 10:43 |
| freemangordon | I am asking because it seems IM support in chromium is broken - no matter how many times I click in the address text field, there is no IM context event generated | 10:52 |
| freemangordon | even in upstream, there is absolutely no mouse/touch events support | 11:02 |
| freemangordon | https://github.com/chromium/chromium/blob/main/ui/gtk/input_method_context_impl_gtk.cc | 11:02 |
| dsc_ | Wizzup: you probably dont have time but getting this to build on ARM would be enable translations (probably) https://github.com/maemo-leste-extras/intgemm/ | 13:41 |
| dsc_ | i am currently sorting some other build related things re: translation project | 13:41 |
| sicelo | so i've been using the droid 4 for calls the last 4 days. works quite well, so i suppose if i had a better battery, i'd be even happier. so yeah, nice work and progress! | 13:50 |
| sicelo | still want to improve support for N900 though :p | 13:50 |
| buZz | i have been using it since april :P | 13:56 |
| Wizzup | dsc_: I can try later tonight | 17:03 |
| uvos | freemangordon: no dident try chomeium | 17:46 |
| uvos | freemangordon: just some regular qt and gtk3 apps | 17:47 |
| uvos | freemangordon: if you are haveing trouble with gtk3 vkb integration i think it makes sense to look at /talk to the phosh implementation/ mantianers | 17:47 |
| uvos | since it works perfectly well there | 17:47 |
| uvos | onboard also somehow manages to raise in firefox, qt and gtk3 applications on archlinux, maybe it makes sense to look at how they do it | 17:48 |
| uvos | looks like onboard uses at-spi + xinput | 17:54 |
| uvos | so not suprizing it works absolutly everywhere | 17:54 |
| uvos | see AtspiStateTracker.py | 17:54 |
| uvos | yes raiseing onboard on chromium works fine | 18:02 |
| uvos | and accerciser (at-spi event viewer) shows chromium is shareing its events on at-spi bus | 18:02 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!