Closed
Bug 750960
Opened 12 years ago
Closed 12 years ago
OMTC: Qt AppShell should use CurrentThread object for event dispatching
Categories
(Core Graveyard :: Widget: Qt, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla15
People
(Reporter: romaxa, Assigned: romaxa)
References
Details
Attachments
(1 file)
1.24 KB,
patch
|
dougt
:
review+
|
Details | Diff | Splinter Review |
Currently nsAppShell dispatcher using qApp->thread() as thread for events dispatching, which is wrong for embedding OMTC setup where we might have qApp in embedding UI thread. and gecko working in different QEventLoop.
Assignee | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
Comment on attachment 620139 [details] [diff] [review] Use QThread::currentThread for events dispatcher Review of attachment 620139 [details] [diff] [review]: ----------------------------------------------------------------- how did this work before? we were processing events on the wrong thread?
Attachment #620139 -
Flags: review?(doug.turner) → review+
Assignee | ||
Comment 3•12 years ago
|
||
default builds are single thread, so AppShell and qApplication working in same thread... also qt main loop with glib backend handle these isssues. this is basically causing problem only with OMTC embedding where qApplication main and appshell work in different threads
Assignee | ||
Updated•12 years ago
|
Keywords: checkin-needed
Comment 5•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/6df779e244c3
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•