|
From: | Daniel J Sebald |
Subject: | Re: GUI - X Error: BadMatch |
Date: | Mon, 28 Jan 2013 15:01:50 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Fedora/3.1.16-1.fc14 Thunderbird/3.1.16 |
On 01/28/2013 02:49 PM, marco atzeri wrote:
On 1/28/2013 9:28 PM, Daniel J Sebald wrote:On 01/28/2013 02:16 PM, marco atzeri wrote:On 1/28/2013 7:00 PM, marco atzeri wrote:[snip]re-testing .... Marcothe only change seems the Resource Id numberMarco, In file-editor-tab.cc replace ->setFocus() with ->setFocus (Qt::OtherFocusReason) and in file-editor.cc replace ->setFocus() with ->setFocus (Qt::ActiveWindowFocusReason) compile and run again. No rhyme or reason to the changes, but perhaps it will reveal where or what is happening. DanDan the second does not exist all "->setFocus" I see are: src/m-editor/file-editor-tab.cc: _edit_area->setFocus (Qt::OtherFocusReason); (changed) src/main-window.cc: _terminal->setFocus (); src/main-window.cc: _terminal_dock_widget->setFocus (); src/main-window.cc: _terminal->setFocus (); src/main-window.cc: _history_dock_widget->setFocus (); src/main-window.cc: _files_dock_widget->setFocus (); src/main-window.cc: _workspace_view->setFocus (); src/main-window.cc: _documentation_dock_widget->setFocus ();
Oh, sorry, I didn't realize that setFocus was used elsewhere. It could be those instances of setFocus which are the issue. I see there are several instances of this combination of lines of code:
_terminal_dock_widget->setFocus (); _terminal_dock_widget->activateWindow ();If you are adventurous, you could swap around the order of one or two of those (activate first, then focus) and see if it affects the number of error messages you are seeing.
Dan
$ hg tip changeset: 15985:f75ffcc82acb tag: tip user: Julien Bect <address@hidden> date: Sun Jan 27 12:29:00 2013 +0100 summary: Added tests for the legacy class system. Regards Marco
-- Dan Sebald email: daniel(DOT)sebald(AT)ieee(DOT)org URL: http://www(DOT)dansebald(DOT)com
[Prev in Thread] | Current Thread | [Next in Thread] |