ravas wrote

I have converted the qg_actionfactory into a function that returns a map of all actions.
I also deleted the createGUIaction function from every action file
and added the code into the action factory. Tedious it was... but worth it.
Moving the "new QAction" code into the actionfactory simplifies all action files,
and allows for the complete removal of the ridiculously long include list...
There is no point in requesting that each action be made,
just make them all at once.

previous action factory:
- receive list of desired actions, and the toolbar / menu to add them to
- request individual actions made elsewhere
- add action to toolbar/menu on arrival

new action factory:
- make all actions
- export them in a container

This is what I would expect from something called an action factory;
and it makes the new menu / toolbar creation function far easier to read and tweak.
RIP to the overly overloaded addGUI function.

---

We haven't been using QActionGroup.
I grouped actions that are linked with the right click feature,
and use the actiongroup's triggered(QAction*) signal
to set the current action.

Right click will step back in the current action and then exit, nothing more.
Stepping back in the actions makes it an overloaded and inconsistent button.
I am thinking about another hotkey to step back in the actions.
Perhaps ctrl + right click.

I have made all the individual toolbars, and a category toolbar with QToolButtons.



This is straightforward Qt stuff—no complex management required!

Next I will implement custom toolbars, and then custom hotkeys.

Hopefully this stuff can go mainstream...