Report an issue that you found while using QLC+ 5.x.
Please provide as many details as you can, a sample workspace if available and don't forget to read the forum posting guidelines first !
Going forward to a v5 release the ux of the vc needs to be improved imho. Although the UI looks/feels the same on different devices (which is great!) the majority of users will still use a keyboard/mouse combo to design the virtual console.
I have two major improvements in mind:
Imho, there should be a context menu on right mouse click offering the same actions as the menu on the right side (e.g., edit/delete). When I tested v5 for the first time, I thought the vc is broken because there is no context menu. I'm sure that others think so as well.
Double clicking a widget opens its properties. Another very common pattern which has also been used in QLC4
I have been looking into the code handling the keyboard inputs. Everything so far seems to be handled on the c++ side and none inside the qml side. It's probably best to keep it that way to keep complexity low.
@Massimo: Having in mind the use case of pressing the delete key, what would be the best approach to open the qml delete confirmation dialog from the c++ side?
Today I've been messing with the implementation of a context menu in the virtual console when it's in edit mode. Here's what I came up with: https://github.com/mcallegari/qlcplus/pull/1209
The context menu dynamically disables or hides options which are not relevant or not available:
vc context menu 3.png (11.67 KiB) Viewed 2479 times
There is one ugly thing: I use "wObj.PIN === undefined" to check whether a specific VCWidgetItem is a cvPage or a real widget. There has to be a better way.
