Last Comment Bug 750284 - WidgetQt Drag service should be initializing in different threads
: WidgetQt Drag service should be initializing in different threads
Status: RESOLVED FIXED
:
Product: Core Graveyard
Classification: Graveyard
Component: Widget: Qt (show other bugs)
: unspecified
: x86 Linux
: -- normal (vote)
: mozilla15
Assigned To: Oleg Romashin (:romaxa)
:
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-30 08:31 PDT by Oleg Romashin (:romaxa)
Modified: 2016-07-11 21:54 PDT (History)
2 users (show)
ryanvm: in‑testsuite-
See Also:
QA Whiteboard:
Iteration: ---
Points: ---


Attachments
Don't init widgets in non main QApp thread (2.20 KB, patch)
2012-04-30 08:32 PDT, Oleg Romashin (:romaxa)
doug.turner: review+
Details | Diff | Splinter Review

Description Oleg Romashin (:romaxa) 2012-04-30 08:31:48 PDT
On attempt to initialize OMTC embedding with Qt toolkit port, I have layout processing mouseMove events and initializing nsDragService Qt in thread which is diffferent from QApplication thread.
I think we should add some basic thread check and don't use any widgets in drag service if QApplication is different from Gecko thread.
Comment 1 Oleg Romashin (:romaxa) 2012-04-30 08:32:49 PDT
Created attachment 619577 [details] [diff] [review]
Don't init widgets in non main QApp thread
Comment 2 Ryan VanderMeulen [:RyanVM] 2012-05-03 03:59:54 PDT
https://hg.mozilla.org/integration/mozilla-inbound/rev/3c8ca7a08274
Comment 3 Ed Morley [:emorley] 2012-05-04 03:58:55 PDT
https://hg.mozilla.org/mozilla-central/rev/3c8ca7a08274

Note You need to log in before you can comment on or make changes to this bug.