**** BEGIN LOGGING AT Sat Jan 14 02:59:57 2012 Jan 14 03:00:30 it resets properly in that branch, hmm Jan 14 03:27:11 I think it's the input being sent into pushKeyEvent Jan 14 03:27:16 like the syms are messed up? Jan 14 03:27:19 but I'm still working on it Jan 14 03:36:49 ah Jan 14 03:36:50 lol Jan 14 03:37:05 vkb: keyUp calls terminal.keyDown :3 Jan 14 03:37:52 oops Jan 14 03:37:53 lol Jan 14 03:38:01 cut and paste fail Jan 14 03:40:38 Brybry, the vkb only sends sym's for modifier keys Jan 14 03:40:40 cut/paste for a merge request? Jan 14 03:40:44 no Jan 14 03:40:50 that was not part of the merge Jan 14 03:50:05 it's still acting weird though Jan 14 03:50:22 works fine for me Jan 14 03:50:28 except modifiers arent doing anything yet Jan 14 03:50:33 but im fixing that Jan 14 03:50:40 like, you know those visual bugs? Jan 14 03:50:44 they aren't just visual anymore ._. Jan 14 03:50:56 ? Jan 14 03:51:56 like for example sometimes when hitting ctrl+shift+c the ctrl key gets stuck down Jan 14 03:52:11 and so the ctl modifier gets stuck Jan 14 03:52:20 (until I press ctrl) Jan 14 03:52:22 well, we will just have to debug this Jan 14 03:52:39 maybe the keys need more gap Jan 14 03:52:40 idk Jan 14 05:15:35 Brybry, dtzWill stbuehler ping Jan 14 05:26:50 hmm? Jan 14 05:27:06 i'm always here Jan 14 05:27:08 :P Jan 14 05:28:32 nm egaudet helped me Jan 14 05:28:48 i have modifiers working like a normal keyboard now Jan 14 05:28:56 well shift and caps at least Jan 14 05:34:58 \o/ Jan 14 05:40:20 just need to fix some caps quirks Jan 14 05:51:15 Brybry, pull my lastest Jan 14 05:51:41 i've got the vkb working with shift/caps Jan 14 05:58:44 hmm Jan 14 05:58:49 something is up with arrow keys Jan 14 05:58:58 ya i was just noticing that Jan 14 05:59:02 i have an idea about that Jan 14 05:59:29 i thought i could get away with just sending keyup for modifier keys Jan 14 06:01:33 Brybry, pull again Jan 14 06:01:35 fixed Jan 14 06:01:55 though im sure there is a way to minimize the code duplication there Jan 14 06:02:53 yup, they're fixed Jan 14 06:05:07 * PuffTheMagic runs cmartix Jan 14 06:07:20 PuffTheMagic: you mentioned things crash if you run cmatrix? Jan 14 06:07:26 coupled with resizing/font changes/etc? Jan 14 06:11:00 ya i havent debugged it Jan 14 06:11:56 i had to extract the ncurses headers from optware and link against a ncurses so from the TP to build it Jan 14 06:12:28 and i ran configure on amd64 box Jan 14 06:12:35 so who know whats wrong Jan 14 06:13:22 ya if i go from portrait to landscape to portrait there is a segfault Jan 14 06:13:40 but on HEAD wterm cmatrix segfaults Jan 14 06:13:47 before wterm segfaulted too Jan 14 06:15:37 well we have a multithreaded application, with the event loop (and rendering) decoupled from the threads that manage the state/read from the terminal Jan 14 06:15:54 and original authors locked all kinds of things, but not the state of sdlcore/etc Jan 14 06:16:07 i'm guessing cmatrix just is constantly updating things on the screen, demanding constant rendering Jan 14 06:16:19 and if you change font/resize/invalidate some things Jan 14 06:16:22 that doesn't play nice Jan 14 06:16:23 maybe? Jan 14 06:16:23 could be Jan 14 06:16:34 shrug, i guess the right answer is to the debug mobile Jan 14 06:16:34 if u need the source and cant find it i can link u to it Jan 14 06:16:45 but like i said, it might become an easter egg Jan 14 06:16:52 haha kk Jan 14 06:17:01 does this happen with any other terminal quick rendering app? Jan 14 06:17:22 ooo i wish i'd thought of this earlier, gotta try aafire Jan 14 06:17:24 or aaxine! Jan 14 06:17:35 wish i'd thought of that earlier so i could do a before/after speed comparison :3 Jan 14 06:17:51 i guess it depends on what u consider quick rendering Jan 14 06:18:01 htop dont crash Jan 14 06:18:06 what is aaxine? Jan 14 06:18:15 yeah, top at 0.1 update speed doesn't crash Jan 14 06:18:22 hmm Jan 14 06:18:22 though I think it gets behind Jan 14 06:18:41 Brybry, nor top at 0.01 Jan 14 06:18:42 ;) Jan 14 06:19:19 ugg Jan 14 06:19:27 i need to fix portrait layout Jan 14 06:21:32 i love github's punchcard Jan 14 06:34:14 nobody likes monday! Jan 14 06:34:24 or saturday :3 Jan 14 06:34:36 I like saturday Jan 14 08:59:51 ka6sox, if you want to test a bluetooth keyboard build: https://github.com/downloads/Brybry/wTerm/us.ryanhope.wterm_0.3.1_bttest.ipk Jan 14 09:00:01 you have to uninstall wterm before installing that Jan 14 09:00:26 and you have to select your keyboard in the preferences Jan 14 10:14:21 did anybody ever think about porting "konsole" for example? it looks to me like the graphic out and the keyboard in could be easily changed, and qt is available, right? Jan 14 10:15:05 otoh, memory usage.. well. Jan 14 10:44:15 stbuehler: where do you get "qt is available, right?" from ? Jan 14 10:52:33 rwhitby: from the libraries in /usr/lib on my device Jan 14 10:53:12 core, gui, network, opengl, script, sql, xml Jan 14 10:56:12 they are used by the app launcher UI - they are not available to webOS apps Jan 14 10:56:41 of course homebrew apps could use them at risk, but there's no guarantee they will stay there Jan 14 14:04:08 sometimes I feel so dumb when the obvious presents itself Jan 14 14:04:59 to solve bt keyboard focus issues all I have to do is catch onKeyDown, pass along that one keypress and set focus Jan 14 14:05:19 :D Jan 14 14:08:36 virtual keyboard keyrepeat complicates matters a little but still it's the right path Jan 14 16:11:33 morn Jan 14 16:19:49 how come no one noticed that i had duplicate ;/: keys on the new keyboard Jan 14 17:48:48 Brybry, wait till u see what i just added to sdlcore Jan 15 00:16:08 lol, I must have been insane last night Jan 15 00:16:46 I was going around the world capturing this keypress and then converting to unicode and sending it to another custom C function or some nonsense Jan 15 00:17:09 just capture the event and redirect it to the proper element...two lines! **** ENDING LOGGING AT Sun Jan 15 02:59:57 2012