| parazyd | Wizzup: pong | 08:22 |
|---|---|---|
| sicelo | https://github.com/robertkirkman/SDL2-bbb-sgx may, or may not be useful here ... dunno | 09:32 |
| Wizzup | sicelo: I assume that's without X then | 14:46 |
| uvos | sdl2 on x works fine for me (for eg. charging-sdl) so idk why we would need anything else | 18:34 |
| uvos | im not sure there is a good testcase for sdl2 on leste | 18:34 |
| uvos | eg. a gles client | 18:34 |
| uvos | maybe we could try compileing supertuxkart with the gles2 backend | 18:35 |
| uvos | or something along those lines | 18:35 |
| uvos | to have a good sdl2 test case | 18:35 |
| uvos | actually neverball uses sdl2 - and i have a gles version that works fine for me | 18:37 |
| Wizzup | uvos: cool, yeah the debian one is not gles iirc | 20:30 |
| inky | uvos, what if you disallow typing several strings with the keyboard? | 20:53 |
| inky | i cannot use pidgin with pinephone | 20:53 |
| inky | it is impossible to send messafe | 20:54 |
| inky | enter does eol in current text, doesnt send pidgin message | 20:54 |
| inky | what if you wait for the first enter and close the keyboard? | 20:55 |
| inky | and send also enter to the window? | 20:55 |
| uvos | "uvos, what if you disallow typing several strings with the keyboard?" not sure what this is supposed to mean | 20:59 |
| uvos | enter types a new line in the vkb, him then sends XK_Return to the application for eatch '\n' in the utf string | 21:00 |
| uvos | so idk why pidgin wouldent work | 21:00 |
| inky | if i type in pidgin window | 21:00 |
| inky | well i dont type right in window, right? | 21:01 |
| inky | i type in onscreen kbd window | 21:01 |
| inky | it allows me to press enter | 21:01 |
| inky | then i get miltiline text | 21:01 |
| uvos | inky: yes | 21:01 |
| uvos | in the vkb you type a string | 21:01 |
| uvos | this string can include '\n' | 21:01 |
| inky | if i get out of vkb | 21:01 |
| inky | i see in pidgin window | 21:02 |
| inky | tdat i typed several lines | 21:02 |
| inky | but i need enter to send it | 21:02 |
| uvos | once you close the vkb that string gets sent to the application by decomposing it into several x keycodes | 21:02 |
| uvos | the '\n' in the string gets decomposed to XK_Return | 21:02 |
| inky | pidgin gets the whole bufyer with lines | 21:02 |
| uvos | no | 21:02 |
| uvos | it dosent | 21:02 |
| uvos | so pidgen gets XK_Return | 21:03 |
| uvos | and lots of other key presses | 21:03 |
| inky | it gets several lines | 21:03 |
| inky | and no way to send the message | 21:03 |
| uvos | no | 21:03 |
| inky | shell i make a video? (: | 21:03 |
| uvos | no | 21:03 |
| uvos | it gets XK_Return how it reacts is a different story... | 21:04 |
| uvos | it might react by adding a newline to its input field | 21:04 |
| uvos | or sending the message | 21:04 |
| uvos | this has nothing to do with the vkb | 21:04 |
| inky | but on droid if i press enter on hwkbd | 21:05 |
| inky | it sends the message | 21:05 |
| uvos | so if i type "ab\nc" the app gets sent XK_A down, XK_A up, XK_B down, XK_B up, XK_Return down, XK_Return up, XK_C down, XK_C up | 21:05 |
| uvos | you can see this in xev | 21:05 |
| inky | wait | 21:05 |
| uvos | inky: https://pastebin.com/BmWzMXvs | 21:13 |
| uvos | here is what xev gets from him for ab\nc | 21:14 |
| uvos | as you can see if your app isent registering enter as you would like it dosent look like it could possibly be hims fault | 21:14 |
| inky | i understand, what is the difference then between droid hwkbd and vkbd? | 21:14 |
| inky | when the enter gets send? | 21:14 |
| inky | you say that pidgin | 21:15 |
| inky | would send severar messages | 21:15 |
| uvos | depends on your pidgin config | 21:15 |
| uvos | you can have it send on shift+enter i think | 21:15 |
| uvos | havent used pidgin in a long time | 21:15 |
| inky | no config for that, seriosly | 21:15 |
| inky | minute | 21:16 |
| uvos | if it works with just return on the hwkbd | 21:16 |
| uvos | then idk | 21:16 |
| uvos | https://pastebin.com/Z5V9cNa2 | 21:17 |
| uvos | thats me typing a b return c on the d4 hwkbd | 21:18 |
| uvos | its the same as the him output | 21:18 |
| uvos | except him types veery fast ofc | 21:18 |
| uvos | there might be bug in pidigin | 21:18 |
| uvos | that triggers when you type so fast that the timestamps dont change | 21:18 |
| uvos | since the timestamps are in ms you cant ever press and release enter within on ms in normal cases | 21:19 |
| uvos | but him can | 21:19 |
| uvos | but thats not hims fault either really | 21:19 |
| uvos | thats the only thing i can think off | 21:20 |
| inky | https://m.youtube.com/watch?v=IT59Mt5IiGQ | 21:20 |
| inky | please look at it | 21:20 |
| uvos | inky: oh your using the hildon backend | 21:21 |
| uvos | yeah thats buggy with apps not desinged for it | 21:21 |
| uvos | use the x11 backend | 21:21 |
| inky | oh how? | 21:21 |
| uvos | open the vkb with search | 21:21 |
| uvos | maybe you cant get to the input field tho | 21:21 |
| inky | waih | 21:21 |
| inky | its default | 21:21 |
| inky | i just reflashed droid's sdcard | 21:22 |
| uvos | hmm what is default? | 21:22 |
| inky | backend | 21:22 |
| inky | yessss | 21:23 |
| inky | when opened with search | 21:23 |
| inky | it sends enter | 21:23 |
| uvos | right | 21:23 |
| inky | but when i touch the text box | 21:23 |
| inky | it doesnt | 21:23 |
| uvos | it uses the libhildon him backend if you touch the box | 21:23 |
| inky | how to change the kbd to always use x11 backend? | 21:23 |
| uvos | and uses the x11 backend if you use search | 21:23 |
| uvos | the way normal hildon him works is pretty fundamentaly broken | 21:24 |
| uvos | it wont work right if the app wasent designed with it in mind | 21:24 |
| inky | on pinephone i hope it'll use the volume button | 21:24 |
| uvos | yeah should work | 21:24 |
| inky | welr if i use the volume button | 21:24 |
| uvos | right | 21:24 |
| inky | it would open vkbd wihh x11 backend | 21:24 |
| uvos | yes | 21:24 |
| inky | why are you keeping hildon backend? | 21:24 |
| inky | why not get cid of it and always use x11 backend? | 21:25 |
| inky | cid/rid | 21:25 |
| uvos | the x11 backend has no way of opening on touch | 21:25 |
| uvos | (of an input field) | 21:25 |
| uvos | atho you could implement this | 21:25 |
| uvos | no way i could ever remove the backend either way, every one here will be out for my head for breaking legacy maemo applications | 21:26 |
| uvos | desktop gtk2 apps will just be sorta broken forever | 21:26 |
| inky | ok i see | 21:26 |
| inky | dont know what to do | 21:26 |
| inky | but cannot imagine that cegular user may want to be informed about two different backends | 21:27 |
| uvos | if you wait long enough desktop gtk2 apps will all disapear | 21:27 |
| uvos | and the problem goes away | 21:27 |
| uvos | or you can go around patching absouly everthing like they did on fremantle | 21:29 |
| marex | hey, I was going through the wiki, but there is one thing I cannot find | 23:35 |
| marex | is there some howto or some such thing on building the whole maemo from scratch ? | 23:35 |
| marex | say, I have a stock debian installation with build-essentials, so, I would like to download the sources and build the packages, likely in some order ? | 23:36 |
| marex | why I'm asking is because I was pondering whether it would be possible to build maemo with OE, there is some meta-maemo already, it is just for maemo4 (i.e. ancient) | 23:36 |
| marex | so, I was pondering whether there is some document where to start with such a build | 23:37 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!