Hi guys,
I think I discovered a bug.
When I am loading attached workspace, open an arbitrary scene, select a fixture and then trying to open the color tool, no color tool appears.
Ubuntu seems to notice that a new window should be opened (another dot next to QLC+ icon), but it is not visible. QLC+ UI is locked, until I use right click on QLC icon on starter -> "Exit 2 Windows". Then, the invisible color tool window is gone and I can use the UI again.
Interestingly, everything works when using a blank new workspace.
Is there something wrong with this workspace file?
Logs do not seem to display anything related.
QLC+ 4.12.7
Tested on:
Ubuntu 22.04.3 LTS
Intel NUC PC
Intel(R) Pentium(R) Silver J5005 CPU @ 1.50GHz
Best regards,
Lukas
Color Tool not visible with special workspace file
-
- Posts: 703
- Joined: Mon Nov 02, 2015 11:03 am
- Location: Germany
- Real Name: Lukas
- Attachments
-
- 2024-01 Zeal 2024.qxw
- (20.74 KiB) Downloaded 177 times
- GGGss
- Posts: 3052
- Joined: Mon Sep 12, 2016 7:15 pm
- Location: Belgium
- Real Name: Fredje Gallon
We lack the fixture profile to do some tests, but I can already say that the color preview for a multi-headed fixture is troublesome.
All electric machines work on smoke... when the smoke escapes... they don't work anymore
- mcallegari
- Posts: 4710
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
I would say you had another display connected and the tool is displayed somewhere outside the main display.
If that's the case, you need to reset the QLC+ settings and the issue is not related to the workspace itself.
If that's the case, you need to reset the QLC+ settings and the issue is not related to the workspace itself.
-
- Posts: 703
- Joined: Mon Nov 02, 2015 11:03 am
- Location: Germany
- Real Name: Lukas
Ah sorry, please find attached
This was not the case, only one display connected.mcallegari wrote: ↑Wed Feb 07, 2024 9:56 am I would say you had another display connected and the tool is displayed somewhere outside the main display.
If that's the case, you need to reset the QLC+ settings and the issue is not related to the workspace itself.
But anyways, how can one reset the QLC+ settings?
- Attachments
-
- Futurelight-Stage-Pixel-Bar-10.qxf
- (16.91 KiB) Downloaded 199 times
- mcallegari
- Posts: 4710
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Settings are basically here (platform-dependent)
https://docs.qlcplus.org/v4/advanced/parameters-tuning
https://docs.qlcplus.org/v4/advanced/parameters-tuning
-
- Posts: 703
- Joined: Mon Nov 02, 2015 11:03 am
- Location: Germany
- Real Name: Lukas
Okay, but this is global for all workspaces, correct? Because when creating a new workspace everything works fine, even with the fixture in question.mcallegari wrote: ↑Wed Feb 07, 2024 11:15 am Settings are basically here (platform-dependent)
https://docs.qlcplus.org/v4/advanced/parameters-tuning
- mcallegari
- Posts: 4710
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Quickly tested on Windows. Works for me with your workspace. Color tool is displayed in the center of the screen.
I think there is something we're missing here but couldn't understand what exactly.
I think there is something we're missing here but couldn't understand what exactly.
-
- Posts: 703
- Joined: Mon Nov 02, 2015 11:03 am
- Location: Germany
- Real Name: Lukas
I quickly tested on Windows as well, there it works for me too...mcallegari wrote: ↑Wed Feb 07, 2024 4:48 pm Quickly tested on Windows. Works for me with your workspace. Color tool is displayed in the center of the screen.
I think there is something we're missing here but couldn't understand what exactly.
It feels like this is more a Qt-relatet thingy. Is there any chance to get more debug output? Tried with console option -d 0/3 but only very few lines there.
- sbenejam
- Posts: 606
- Joined: Sun Apr 12, 2015 6:28 pm
- Real Name: Santiago Benejam Torres
- Contact:
On Ubuntu 22.04, KDE Plasma (x11) and QLC+ 4.12.8-GIT It works as expected.
- mcallegari
- Posts: 4710
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Here's Linux too.
No idea what's going on in your Ubuntu. Perhaps look at Qt settings in your
No idea what's going on in your Ubuntu. Perhaps look at Qt settings in your
Code: Select all
$HOME/.local/share/
-
- Posts: 703
- Joined: Mon Nov 02, 2015 11:03 am
- Location: Germany
- Real Name: Lukas
Okay this is really strange. I did a lot of fiddling the xml code to find out that actually the SpeedDial widget in VC is causing the trouble.
If I delete it in the _broken file, everything is back to normal.
If I create a SpeedDial widget in the _works file, everything still works until I re-open the file, then it is broken as well.
I have attached a picture of how the "stuck" Color Tool window looks like on my ubuntu.
In addition, a screenshot of how the color tool looks on my side when opened normally (this is different from your screenshot so just wanted to point this out).
If I delete it in the _broken file, everything is back to normal.
If I create a SpeedDial widget in the _works file, everything still works until I re-open the file, then it is broken as well.
I have attached a picture of how the "stuck" Color Tool window looks like on my ubuntu.
In addition, a screenshot of how the color tool looks on my side when opened normally (this is different from your screenshot so just wanted to point this out).
- Attachments
-
- 2024-01 Zeal 2024_works.qxw
- (19.21 KiB) Downloaded 198 times
-
- 2024-01 Zeal 2024_broken.qxw
- (19.69 KiB) Downloaded 180 times
- mcallegari
- Posts: 4710
- Joined: Sun Apr 12, 2015 9:09 am
- Location: Italy
- Real Name: Massimo Callegari
- Contact:
Do you have a GitHub account?
Can you please try the latest build from GitHub Actions?
That looks like a Qt issue/incompatibility
Can you please try the latest build from GitHub Actions?
That looks like a Qt issue/incompatibility
-
- Posts: 703
- Joined: Mon Nov 02, 2015 11:03 am
- Location: Germany
- Real Name: Lukas
Just realised that this version produces some UI Glitches as shown in attached screenshots, so I guess it won't be released too soon...
- Attachments
-
- Bildschirmfoto vom 2024-02-19 03-39-12.png (9.11 KiB) Viewed 3322 times
-
- Posts: 2
- Joined: Mon Jan 29, 2024 6:03 pm
- Real Name:
Dear all,
this thread is already some days old. But not sure of this has been finally solved for "siegmund". I now have same problem when changing from Linux Mint 21.3 to 22.0. So far what I could found out, The "color select" dialog in m working scenario (Mint 21.3) is the QT dialog. The none working "color select" dialog seems to be the native one. I installed both Linux versions so I can switch between working and none working. If I use the working Linux version "Linux Mint 21.3" I cn crete the issue when starting qlcplus with the paramter " -platformtheme none". Which seems to force the native dialog. But I haven't found a start parameter to force "QT DIalog".
BTW: If I say "none working" I mean same behvior as "siegmund" described related to the "Speed dialer" - see above. Even re- compiling from Github did not help.
Hopefully somebody has an idea.
Kind regards.
this thread is already some days old. But not sure of this has been finally solved for "siegmund". I now have same problem when changing from Linux Mint 21.3 to 22.0. So far what I could found out, The "color select" dialog in m working scenario (Mint 21.3) is the QT dialog. The none working "color select" dialog seems to be the native one. I installed both Linux versions so I can switch between working and none working. If I use the working Linux version "Linux Mint 21.3" I cn crete the issue when starting qlcplus with the paramter " -platformtheme none". Which seems to force the native dialog. But I haven't found a start parameter to force "QT DIalog".
BTW: If I say "none working" I mean same behvior as "siegmund" described related to the "Speed dialer" - see above. Even re- compiling from Github did not help.
Hopefully somebody has an idea.
Kind regards.
-
- Posts: 2
- Joined: Mon Jan 29, 2024 6:03 pm
- Real Name:
Not sure, if somebody still has this issue and is looking for a solution,but I found it in the meantime and want to share it with you. I another forum I found somebody complaining, that after installing Linux Mint 22 Qt ist not properly working. The proposed solution was the following:
1) Install "qt5ct" sudo apt install qt5ct
2) After that add following line to file /etc/environment : QT_QPA_PLATFORMTHEME=qt5ct
3) Reboot system
Exact steps helped with my problem. So hopefully this helps also others.
1) Install "qt5ct" sudo apt install qt5ct
2) After that add following line to file /etc/environment : QT_QPA_PLATFORMTHEME=qt5ct
3) Reboot system
Exact steps helped with my problem. So hopefully this helps also others.