i am not sure myself, but i have seen maemo send me to desktop after a quick press of "home", something only a long press should do.
and your description of only a single window of tear closing is consistent with a long press of "back", as i was probably in error claiming that the app would close (tho mostly one uses a app with only a single window).
oh, and that gtk message is probably unrelated, as it shows up on opening of the first window, and on the closing of the last, no matter how said window is closed.
it do not however shows up when closing any other tear window...
please make links long press or double press or make it selectable how to activate a link because let me tell you what just happened. I spent 15 minutes typing out 3 paragraphs about details of how i would improve this house to a home improvement tv show website and then I temporarily set the N810 down to think and change the channel on my pc/tv and then i picked the N810 back up and accidentally i guess hit something on the edge of the screen sending me somewhere else and wiping eveything out that i just typed. That is very very extremely annoying! You want to be innovative? Put a menu item on this tear browser called "typing lock" that keeps the touchscreen from activating if you need to set down the N and pick it back up later or maybe even better auto commence touch screen lock upon clicking within a text entry field until submit is clicked. wow i can't believe i completed this post without accidentally getting launched to some other link.
do said screen lock only lck the screen input, or will it also lock the keyboard? i only own a n800, but experience suggests that a lock like that also locks other inputs...
do said screen lock only lck the screen input, or will it also lock the keyboard?
It locks the screen, keyboard, and all other buttons, just as the "Lock touch screen and keys" option on the N800 does. It's just a faster, more reliable way of accessing that function.
I added some traces in Tear event handlers.
It seems tso was right.
When I press the "back" button (short press), sometimes tear receives a key_down event, and then about a second later, a delete event (which causes the current window to close), and then a key_up event.
So it looks like a problem outside Tear (but i've never noticed it with any other application).
As I'm the only one with this problem, i'll just patch my copy of tear to disable window closing on "back" long press and won't bother you again with this
btw Bundyo, it would be nice to publish up to date webkit dev package in some repository to enable people to easily hack with tear code
