Please help with actual C++ code
-
This post is deleted!
@AnneRanch said in Please help with actual C++ code:
I have been told I cannot have "check box : in main menu
You can have a checkbox on an action in any menu, "main" or not. These are created via
QMenu::addAction().However, if you instead add an item which is a submenu (a > that you click on to display a "slide-out" menu) you cannot have a checkbox on that item. These are created via
QMenu::addMenu(). And if you think about it, what would be the point of having a checkbox on a menu item which just displays a submenu anyway? -
@AnneRanch said in Please help with actual C++ code:
I have been told I cannot have "check box : in main menu
You can have a checkbox on an action in any menu, "main" or not. These are created via
QMenu::addAction().However, if you instead add an item which is a submenu (a > that you click on to display a "slide-out" menu) you cannot have a checkbox on that item. These are created via
QMenu::addMenu(). And if you think about it, what would be the point of having a checkbox on a menu item which just displays a submenu anyway?This post is deleted! -
This post is deleted!
This post is deleted! -
reading this generally,
@AnneRanch said in Please help with actual C++ code:
The widow just do part of the interface and then I will oopen anither widow to continue... eventually all windows will comlete the required task. So when it is all done I can close it and it would be nice to reopen ALL of then at once when required...hence I thought it could be done in main window...
The whole idea to have uncluttered interaction as required -- one window At the time...I have the strong suspicion you're trying to implement a GUI idea using existing components which are not actually meant to be used like that at all.
Specifically, QMenu and its related classes are NOT supposed to be used like windows. You're not going to get a good user experience using this kind of windows.If you share your GUI idea you might get suggestions on how to approach the app.
I suspect a QML component will give you a LOT more flexibility that will allow you to get a good user experience.
-
reading this generally,
@AnneRanch said in Please help with actual C++ code:
The widow just do part of the interface and then I will oopen anither widow to continue... eventually all windows will comlete the required task. So when it is all done I can close it and it would be nice to reopen ALL of then at once when required...hence I thought it could be done in main window...
The whole idea to have uncluttered interaction as required -- one window At the time...I have the strong suspicion you're trying to implement a GUI idea using existing components which are not actually meant to be used like that at all.
Specifically, QMenu and its related classes are NOT supposed to be used like windows. You're not going to get a good user experience using this kind of windows.If you share your GUI idea you might get suggestions on how to approach the app.
I suspect a QML component will give you a LOT more flexibility that will allow you to get a good user experience.
@TomZ Thanks, however... I am just extending "windows
...tile...cascade..." menu using mdiArea (example). I have it essentially working, include "connect". The "problem is " - it can be started with QMenu -that makes submenu extension easy - but adding "checkable " to sub menu is currently failing. Or I can start with QAction then adding depended sub menu fails. Right now I feel starting with "cascading menus " is cleaner ..in case I want to add sususbsub....
The "user" -me - has several depended tasks to accomplish - setup serial connection, then setup dependent Bluetooth connection, configure remote Bluetooth device and then attach it to "serial connection" etc.,key remote device - amateur radio transmitter, listen to "meteor scatter" pings on Internet ...
The basic idea is to do all this in separate forms , I got that going, to keep monitor and me , focused on task... -
@TomZ Thanks, however... I am just extending "windows
...tile...cascade..." menu using mdiArea (example). I have it essentially working, include "connect". The "problem is " - it can be started with QMenu -that makes submenu extension easy - but adding "checkable " to sub menu is currently failing. Or I can start with QAction then adding depended sub menu fails. Right now I feel starting with "cascading menus " is cleaner ..in case I want to add sususbsub....
The "user" -me - has several depended tasks to accomplish - setup serial connection, then setup dependent Bluetooth connection, configure remote Bluetooth device and then attach it to "serial connection" etc.,key remote device - amateur radio transmitter, listen to "meteor scatter" pings on Internet ...
The basic idea is to do all this in separate forms , I got that going, to keep monitor and me , focused on task... -
This post is deleted!
@AnneRanch said in Please help with actual C++ code:
subMenu[index]->addAction(list_array[index][ 2] + " #" + QString::number( index_sub));...returns a
QAction *. You need to store this pointer to connect to the action'striggeredsignal. Then you can skip the whole acrobatics about gettingindexinside a slot.Do you understand that?
-
This post is deleted!
-
@AnneRanch
but I am unable to add "check box" to any of them
QAction *action = submenu[index]->addAction("Some text"); action->setCheckable(true);adds an action with text
Some textand sets it to have a checkbox.This post is deleted! -
This post is deleted!
This post is deleted! -
A Axel Spoerl referenced this topic on
