Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Qt4 style fails if GTK main event loop runs on a secondary thread #69

Open
GoogleCodeExporter opened this issue Mar 14, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Using the Qt4 style in any GTK2 application where the GTK main event loop runs
in a secondary thread, such as gnuplot or the viewers of the LTI-Lib-2

The following errors appear:

QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPainter::begin: Cannot paint on a null pixmap
QPainter::pen: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::setPen: Painter not active
QPainter::end: Painter not active, aborted

It seems that the style way of catching up the gtk-calls runs them in the wrong
thread, producing not only tons those error messages, but incorrectly painting
scrollbars, buttons, etc.

Workaround

Using QtCurve, Clearlooks or any other style correctly displays the dialogs and
avoids producing the errors.

What steps will reproduce the problem?

1. Start a KDE4 session 
2. Run gnuplot and execute "test"
3. The problem also appears running any application/example of the LTI-Lib 2 (an
image processing library)

Which Qt style are you using?

Qt4

Original issue reported on code.google.com by [email protected] on 4 Jul 2009 at 5:13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant