Avoid Qt bug by using onAfterRendering instead of onAfterSynchronizing to display dialogs
This commit is contained in:
parent
e182445593
commit
113751a4bc
1 changed files with 4 additions and 1 deletions
|
|
@ -82,7 +82,10 @@ ApplicationWindow {
|
||||||
|
|
||||||
property bool initialized: false
|
property bool initialized: false
|
||||||
|
|
||||||
onAfterSynchronizing: {
|
// BUG: Using onAfterSynchronizing: here causes very strange
|
||||||
|
// failures on Linux. Many shaders fail to compile and we
|
||||||
|
// eventually segfault deep inside the Qt OpenGL code.
|
||||||
|
onAfterRendering: {
|
||||||
// We use this callback to trigger dialog display because
|
// We use this callback to trigger dialog display because
|
||||||
// it only happens once the window is fully constructed.
|
// it only happens once the window is fully constructed.
|
||||||
// Doing it earlier can lead to the dialog appearing behind
|
// Doing it earlier can lead to the dialog appearing behind
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue