Re: Why touch event go through my window
On Tue, 2010-02-16 at 16:07 +0100, ext Evan JIANG wrote: > Yes. I've tried that. > But I still have no idea why it crashes on your device. > It works well here. > I'm not sure, but maybe you can try: > 1. rm -rf /home/user/.scim > And reboot to check if it works. > 2. Reinstall it. > Since someone said it works for him before: > http://code.google.com/p/scim-for-maemo/issues/detail?id=22&can=1 > (Comment 8) > > I'm trying to reproduce and fix it now. > I will let you know if I have any progress on it. I tracked down the failure a bit, it seems that PanelAgent::initialize() is failing. So it means that m_socket_server.create() returns false for some reason. -Kimmo > > Thank you very much! > > Best regards, > Evan JIANG > 2010/2/16 Kimmo Hämäläinen : > > On Tue, 2010-02-16 at 10:34 +0100, ext Evan JIANG wrote: > >> Hi, > >> Thank you for your reply. > >> Which locale are you using? > >> It's ok to run it under en_US on real device. The application is > >> using by lots of users for 2 monthes. I think it should not have such > >> problem. > >> The source code can be found here: > >> http://code.google.com/p/scim-for-maemo/ > >> Well, I admit the source code is a bit complex. > > > > I compiled the mscim package from this Subversion trunk, but it is still > > crashing after I have installed it. Have you used it in a fresh PR1.1 > > N900 by just installing those two packages, nothing more? > > > > -Kimmo > > > > > > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
Yes. I've tried that. But I still have no idea why it crashes on your device. It works well here. I'm not sure, but maybe you can try: 1. rm -rf /home/user/.scim And reboot to check if it works. 2. Reinstall it. Since someone said it works for him before: http://code.google.com/p/scim-for-maemo/issues/detail?id=22&can=1 (Comment 8) I'm trying to reproduce and fix it now. I will let you know if I have any progress on it. Thank you very much! Best regards, Evan JIANG 2010/2/16 Kimmo Hämäläinen : > On Tue, 2010-02-16 at 10:34 +0100, ext Evan JIANG wrote: >> Hi, >> Thank you for your reply. >> Which locale are you using? >> It's ok to run it under en_US on real device. The application is >> using by lots of users for 2 monthes. I think it should not have such >> problem. >> The source code can be found here: http://code.google.com/p/scim-for-maemo/ >> Well, I admit the source code is a bit complex. > > I compiled the mscim package from this Subversion trunk, but it is still > crashing after I have installed it. Have you used it in a fresh PR1.1 > N900 by just installing those two packages, nothing more? > > -Kimmo > > > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
On Tue, 2010-02-16 at 10:34 +0100, ext Evan JIANG wrote: > Hi, > Thank you for your reply. > Which locale are you using? > It's ok to run it under en_US on real device. The application is > using by lots of users for 2 monthes. I think it should not have such > problem. > The source code can be found here: http://code.google.com/p/scim-for-maemo/ > Well, I admit the source code is a bit complex. I compiled the mscim package from this Subversion trunk, but it is still crashing after I have installed it. Have you used it in a fresh PR1.1 N900 by just installing those two packages, nothing more? -Kimmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
Because I want the window has a white board around it. If I don't set the window type hint, the window itself will be just a pure window with no board. Even set the board width doesn't work. But for sure that I've tried to remove these code to make sure the bug is not caused by these code. And I found these code is not related to the bug. Best regards, Evan JIANG 2010/2/16 Claudio Saavedra : > You first commented: > > El sáb, 06-02-2010 a las 23:53 +0800, Evan JIANG escribió: >> >> My panel is created with gtk_window_new (GTK_WINDOW_POPUP); > > And then said: > > El mar, 16-02-2010 a las 01:06 +0800, Evan JIANG escribió: >> >> gtk_window_set_type_hint (GTK_WINDOW (_input_window), >> GDK_WINDOW_TYPE_HINT_DIALOG); > > Why do you need to mess with the window types so much? Can you try > simplifying that? > > Claudio > > > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
You first commented: El sáb, 06-02-2010 a las 23:53 +0800, Evan JIANG escribió: > > My panel is created with gtk_window_new (GTK_WINDOW_POPUP); And then said: El mar, 16-02-2010 a las 01:06 +0800, Evan JIANG escribió: > > gtk_window_set_type_hint (GTK_WINDOW (_input_window), > GDK_WINDOW_TYPE_HINT_DIALOG); Why do you need to mess with the window types so much? Can you try simplifying that? Claudio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
On Tue, 2010-02-16 at 10:34 +0100, ext Evan JIANG wrote: > Hi, > Thank you for your reply. > Which locale are you using? > It's ok to run it under en_US on real device. The application is > using by lots of users for 2 monthes. I think it should not have such > problem. > The source code can be found here: http://code.google.com/p/scim-for-maemo/ > Well, I admit the source code is a bit complex. I had "fi_FI". I tried with "en_US" but it crashes with that also... I think it should not crash whatever the locale is, don't you agree? -Kimmo > > Best regards, > Evan JIANG > > 2010/2/16 Kimmo Hämäläinen : > > On Mon, 2010-02-15 at 18:06 +0100, ext Evan JIANG wrote: > >> Hi, > > ... > >> The application is in mameo extras-devel repository. Could you help me > >> to test that? > >> You can get it from > >> http://repository.maemo.org/extras-devel/pool/fremantle/free/m/mscim/mscim_1.4.7-1maemo5_armel.deb > >> It's not the latest version in the repository. Because I've applied my > >> workaround since > >> mscim_1.4.7-1maemo6_armel, you need to try one before version > >> 1.4.7-1maemo6. > >> And please also install mscim-googlepinyin package from maemo > >> extras-devel repository. The input method only works after both of > >> these 2 packages are installed. > > > > I installed mscim-googlepinyin 0.11.10-1maemo3 and mscim 1.4.7-1maemo5 > > but it is not working. scim-panel-gtk is crashing with signal 6. I > > attached the syslog with one message. > > > > I tried with our latest Maemo5 version and with 51-1 image but the same > > thing happens in both. > > > > How to get it to run? > > > > -Kimmo > > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
Hi, Thank you for your reply. Which locale are you using? It's ok to run it under en_US on real device. The application is using by lots of users for 2 monthes. I think it should not have such problem. The source code can be found here: http://code.google.com/p/scim-for-maemo/ Well, I admit the source code is a bit complex. Best regards, Evan JIANG 2010/2/16 Kimmo Hämäläinen : > On Mon, 2010-02-15 at 18:06 +0100, ext Evan JIANG wrote: >> Hi, > ... >> The application is in mameo extras-devel repository. Could you help me >> to test that? >> You can get it from >> http://repository.maemo.org/extras-devel/pool/fremantle/free/m/mscim/mscim_1.4.7-1maemo5_armel.deb >> It's not the latest version in the repository. Because I've applied my >> workaround since >> mscim_1.4.7-1maemo6_armel, you need to try one before version 1.4.7-1maemo6. >> And please also install mscim-googlepinyin package from maemo >> extras-devel repository. The input method only works after both of >> these 2 packages are installed. > > I installed mscim-googlepinyin 0.11.10-1maemo3 and mscim 1.4.7-1maemo5 > but it is not working. scim-panel-gtk is crashing with signal 6. I > attached the syslog with one message. > > I tried with our latest Maemo5 version and with 51-1 image but the same > thing happens in both. > > How to get it to run? > > -Kimmo > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
On Mon, 2010-02-15 at 18:06 +0100, ext Evan JIANG wrote: > Hi, ... > The application is in mameo extras-devel repository. Could you help me > to test that? > You can get it from > http://repository.maemo.org/extras-devel/pool/fremantle/free/m/mscim/mscim_1.4.7-1maemo5_armel.deb > It's not the latest version in the repository. Because I've applied my > workaround since > mscim_1.4.7-1maemo6_armel, you need to try one before version 1.4.7-1maemo6. > And please also install mscim-googlepinyin package from maemo > extras-devel repository. The input method only works after both of > these 2 packages are installed. I installed mscim-googlepinyin 0.11.10-1maemo3 and mscim 1.4.7-1maemo5 but it is not working. scim-panel-gtk is crashing with signal 6. I attached the syslog with one message. I tried with our latest Maemo5 version and with 51-1 image but the same thing happens in both. How to get it to run? -Kimmo Feb 16 10:39:47 Nokia-N900-51-1 scim-panel-gtk[1558]: GLIB WARNING ** Gtk - Locale not supported by C library. ^IUsing the fallback 'C' locale. Failed to initialize Panel Agent! Feb 16 10:39:51 Nokia-N900-51-1 crash_reporter_daemon[1294]: [creporter_get_rcore_fileinfo]: File: /home/user/MyDocs/core-dumps/scim-panel-gtk-6BF7-6-1463.rcore.lzo size 624089 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
Hi, Reply inline. 2010/2/15 Kimmo Hämäläinen : > On Sun, 2010-02-14 at 04:09 +0100, ext Evan JIANG wrote: >> Thank you for your reply. >> Since I'm on travel now, I may could only try it some days later. >> >> I guess it's cause by the browser and hildon-desktop called some >> matchbox API directly, that >> maybe some MB APIs could hide the window and the window can not be >> shown again with GTK APIs. > > No, there are no Matchbox(2) APIs used by applications. (The API is not > even available at all because the libmatchbox2 library is statically > linked to hildon-desktop, so no application is able to dynamically link > to it.) I said that because of I saw "#include " and lots of APIs like "mb_wm_*" in hildon-desktop source code. The code is from http://maemo.gitorious.org/fremantle-hildon-desktop . > > My guess about your "ghost window" is that the X window stacking does > not match what the compositor shows on the screen. So it could be a bug > in hildon-desktop, or it could be some unsupported window type (that's > why I asked for xprop and xwininfo outputs). > >> I found everything works well with FireFox borwser for Maemo. > > That is interesting... Have you tried the N900 browser in fullscreen > mode, does it work then? No, it has the same problem in N900 browser with fullscreen mode. > >> Here I could give more details about the window lifecycle. >> There's a scim-gtk-panel daemon which will auto start when system startup. >> When the daemon starts, it will create a winodw, and hide it immediately. >> Everytime when the input method need to show the input window, it will send >> command to the daemon to show the input window and move it to the front. >> When the inputing is done and edit field loses the focus, the input window >> will >> be hidden by calling "gtk_widget_hide" > > This should work if the window is supported by the window manager (to > see that I need the xprop & xwininfo outputs or a test program from > you). I did these on my window: " gtk_window_set_type_hint (GTK_WINDOW (_input_window), GDK_WINDOW_TYPE_HINT_DIALOG); gtk_widget_set_name (_input_window, "hildon-input-method-ui"); " But I've tried to comment these lines or change to other types or names. It has the same problem. > >> This design works all right on most of PC Desktop Linux. As I said, >> it also works >> well for most applications on Maemo, except browser. In the Browser >> application, >> when the input window is showing, and I click on other places to close >> the window, >> the window won't show again with "gtk_widget_show_all". >> >> My current workaround is, when the input window need to be hidden, I >> will destroy >> the window, and next time when it need to be shown, I will create the >> window again. >> With this workaround, it works just OK now. But, the performance is >> much worse than >> before, since creating and destroying the window take longer time. > > This workaround should not be necessary. We have many such windows, for > example the "Select Connection" dialog that you use to select connection > to the Internet. It sounds like the window type is confusing to the > window manager and it does not behave right in this case. > The application is in mameo extras-devel repository. Could you help me to test that? You can get it from http://repository.maemo.org/extras-devel/pool/fremantle/free/m/mscim/mscim_1.4.7-1maemo5_armel.deb It's not the latest version in the repository. Because I've applied my workaround since mscim_1.4.7-1maemo6_armel, you need to try one before version 1.4.7-1maemo6. And please also install mscim-googlepinyin package from maemo extras-devel repository. The input method only works after both of these 2 packages are installed. After install these packages, you need to reboot the device. Focus in an edit field, and press keys will show the input window. Maybe you will need ctrl+space to turn on the input method. It's a Chinese input method, but I think you don't need to care that. Like, you can just press "a" to test. Here is howto reproduce the problem: 1.Launch N900 browser, and goto google homepage. 2.Click the search field to make it able to input. 3.Press "a" with hard keyboard. The input window should show now. 4.Click other places in the web page, but not the edit field and inside the input window. The input window will be hidden now. Or maybe sometimes even you click the buttons in input window, the problem will happen, too. Then, no way to show the input window again. If you do the same steps in other applications like "conversation" - "New SMS", the input window will still show when you next time press "a". Not sure if these informations are enought. Thank you very much for your help. Best regards, Evan JIANG > -Kimmo > >> >> Best regards, >> Evan JIANG >> 2010/2/12 Kimmo Hämäläinen : >> > On Sat, 2010-02-06 at 16:53 +0100, ext Evan JIANG wrote: >> >> Hi all, >> >> I'm developing an input method for N900. >> >> The main window is not full screen, and
Re: Why touch event go through my window
On Sun, 2010-02-14 at 04:09 +0100, ext Evan JIANG wrote: > Thank you for your reply. > Since I'm on travel now, I may could only try it some days later. > > I guess it's cause by the browser and hildon-desktop called some > matchbox API directly, that > maybe some MB APIs could hide the window and the window can not be > shown again with GTK APIs. No, there are no Matchbox(2) APIs used by applications. (The API is not even available at all because the libmatchbox2 library is statically linked to hildon-desktop, so no application is able to dynamically link to it.) My guess about your "ghost window" is that the X window stacking does not match what the compositor shows on the screen. So it could be a bug in hildon-desktop, or it could be some unsupported window type (that's why I asked for xprop and xwininfo outputs). > I found everything works well with FireFox borwser for Maemo. That is interesting... Have you tried the N900 browser in fullscreen mode, does it work then? > Here I could give more details about the window lifecycle. > There's a scim-gtk-panel daemon which will auto start when system startup. > When the daemon starts, it will create a winodw, and hide it immediately. > Everytime when the input method need to show the input window, it will send > command to the daemon to show the input window and move it to the front. > When the inputing is done and edit field loses the focus, the input window > will > be hidden by calling "gtk_widget_hide" This should work if the window is supported by the window manager (to see that I need the xprop & xwininfo outputs or a test program from you). > This design works all right on most of PC Desktop Linux. As I said, > it also works > well for most applications on Maemo, except browser. In the Browser > application, > when the input window is showing, and I click on other places to close > the window, > the window won't show again with "gtk_widget_show_all". > > My current workaround is, when the input window need to be hidden, I > will destroy > the window, and next time when it need to be shown, I will create the > window again. > With this workaround, it works just OK now. But, the performance is > much worse than > before, since creating and destroying the window take longer time. This workaround should not be necessary. We have many such windows, for example the "Select Connection" dialog that you use to select connection to the Internet. It sounds like the window type is confusing to the window manager and it does not behave right in this case. -Kimmo > > Best regards, > Evan JIANG > 2010/2/12 Kimmo Hämäläinen : > > On Sat, 2010-02-06 at 16:53 +0100, ext Evan JIANG wrote: > >> Hi all, > >>I'm developing an input method for N900. > >>The main window is not full screen, and looks like this: > >> http://www.evan129.com/wp-content/uploads/2009/12/20091225_d151774f028f00e741aecdywcKr7OnKn.png > >>It works well in most of times. But in browser application, it's a > >> bit strange. > >> > >>As you can see, there are some buttons in the panel, users can > >> press the buttons to choose the words. In browser application, > >> when users pressed the button, the event will go through my window to > >> the browser. Then because of the press location is not in the same > >> edit field, the edit field will lose the focus. > >> > >> I may not explained it clearly. Let me give an easier understanding > >> example. If the window is in the top of screen, covered the title bar, > >> then when I press the button on the left-top > >> corner, it will show the application switch window. That means, the > >> press event go through my window, and handled by the app swithcer > >> button. > > > > What's the output of these commands for your window: > > > > xprop -id > > xwininfo -id > > > > These command line tools can be found from x11-utils package. > > > > -Kimmo > > > >> > >> These are the only 2 places I found that could receive my press event. > >> But in all other places, I didn't find this happening. > >> > >> My panel is created with gtk_window_new (GTK_WINDOW_POPUP); > >> And the buttons are created by gtk_button_new();. I use > >> g_signal_connect to receive the "clicked" event or > >> "button-press-event" event. > >> > >> Does anyone have any idea about that? > >> > >> Best regards, > >> Evan JIANG > >> ___ > >> maemo-developers mailing list > >> maemo-developers@maemo.org > >> https://lists.maemo.org/mailman/listinfo/maemo-developers > > > > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
Thank you for your reply. Since I'm on travel now, I may could only try it some days later. I guess it's cause by the browser and hildon-desktop called some matchbox API directly, that maybe some MB APIs could hide the window and the window can not be shown again with GTK APIs. I found everything works well with FireFox borwser for Maemo. Here I could give more details about the window lifecycle. There's a scim-gtk-panel daemon which will auto start when system startup. When the daemon starts, it will create a winodw, and hide it immediately. Everytime when the input method need to show the input window, it will send command to the daemon to show the input window and move it to the front. When the inputing is done and edit field loses the focus, the input window will be hidden by calling "gtk_widget_hide" This design works all right on most of PC Desktop Linux. As I said, it also works well for most applications on Maemo, except browser. In the Browser application, when the input window is showing, and I click on other places to close the window, the window won't show again with "gtk_widget_show_all". My current workaround is, when the input window need to be hidden, I will destroy the window, and next time when it need to be shown, I will create the window again. With this workaround, it works just OK now. But, the performance is much worse than before, since creating and destroying the window take longer time. Best regards, Evan JIANG 2010/2/12 Kimmo Hämäläinen : > On Sat, 2010-02-06 at 16:53 +0100, ext Evan JIANG wrote: >> Hi all, >> I'm developing an input method for N900. >> The main window is not full screen, and looks like this: >> http://www.evan129.com/wp-content/uploads/2009/12/20091225_d151774f028f00e741aecdywcKr7OnKn.png >> It works well in most of times. But in browser application, it's a >> bit strange. >> >> As you can see, there are some buttons in the panel, users can >> press the buttons to choose the words. In browser application, >> when users pressed the button, the event will go through my window to >> the browser. Then because of the press location is not in the same >> edit field, the edit field will lose the focus. >> >> I may not explained it clearly. Let me give an easier understanding >> example. If the window is in the top of screen, covered the title bar, >> then when I press the button on the left-top >> corner, it will show the application switch window. That means, the >> press event go through my window, and handled by the app swithcer >> button. > > What's the output of these commands for your window: > > xprop -id > xwininfo -id > > These command line tools can be found from x11-utils package. > > -Kimmo > >> >> These are the only 2 places I found that could receive my press event. >> But in all other places, I didn't find this happening. >> >> My panel is created with gtk_window_new (GTK_WINDOW_POPUP); >> And the buttons are created by gtk_button_new();. I use >> g_signal_connect to receive the "clicked" event or >> "button-press-event" event. >> >> Does anyone have any idea about that? >> >> Best regards, >> Evan JIANG >> ___ >> maemo-developers mailing list >> maemo-developers@maemo.org >> https://lists.maemo.org/mailman/listinfo/maemo-developers > > ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
On Sat, 2010-02-06 at 16:53 +0100, ext Evan JIANG wrote: > Hi all, >I'm developing an input method for N900. >The main window is not full screen, and looks like this: > http://www.evan129.com/wp-content/uploads/2009/12/20091225_d151774f028f00e741aecdywcKr7OnKn.png >It works well in most of times. But in browser application, it's a > bit strange. > >As you can see, there are some buttons in the panel, users can > press the buttons to choose the words. In browser application, > when users pressed the button, the event will go through my window to > the browser. Then because of the press location is not in the same > edit field, the edit field will lose the focus. > > I may not explained it clearly. Let me give an easier understanding > example. If the window is in the top of screen, covered the title bar, > then when I press the button on the left-top > corner, it will show the application switch window. That means, the > press event go through my window, and handled by the app swithcer > button. What's the output of these commands for your window: xprop -id xwininfo -id These command line tools can be found from x11-utils package. -Kimmo > > These are the only 2 places I found that could receive my press event. > But in all other places, I didn't find this happening. > > My panel is created with gtk_window_new (GTK_WINDOW_POPUP); > And the buttons are created by gtk_button_new();. I use > g_signal_connect to receive the "clicked" event or > "button-press-event" event. > > Does anyone have any idea about that? > > Best regards, > Evan JIANG > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
On Fri, 2010-02-12 at 16:30 +0100, ext Thomas Perl wrote: > 2010/2/6 Evan JIANG : > > I may not explained it clearly. Let me give an easier understanding > > example. If the window is in the top of screen, covered the title bar, > > then when I press the button on the left-top > > corner, it will show the application switch window. That means, the > > press event go through my window, and handled by the app swithcer > > button. > > Maybe calling XSetInputFocus helps here? See this thread: Nope, XSetInputFocus affects the keyboard input only, not window stacking order. -Kimmo > > http://sourceforge.net/mailarchive/forum.php?thread_name=c4cd0cc80911291029l282b140fob3288389beabfa39%40mail.gmail.com&forum_name=enlightenment-devel > > Also: > > http://forums.internettablettalk.com/showthread.php?t=36952 > https://bugs.maemo.org/show_bug.cgi?id=6511 > > HTH. > > Thomas > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Why touch event go through my window
2010/2/6 Evan JIANG : > I may not explained it clearly. Let me give an easier understanding > example. If the window is in the top of screen, covered the title bar, > then when I press the button on the left-top > corner, it will show the application switch window. That means, the > press event go through my window, and handled by the app swithcer > button. Maybe calling XSetInputFocus helps here? See this thread: http://sourceforge.net/mailarchive/forum.php?thread_name=c4cd0cc80911291029l282b140fob3288389beabfa39%40mail.gmail.com&forum_name=enlightenment-devel Also: http://forums.internettablettalk.com/showthread.php?t=36952 https://bugs.maemo.org/show_bug.cgi?id=6511 HTH. Thomas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
