Q Light Controller+

There seems to be some basic functionality that I would like to see able to be controlled via an external board,
The bits I would like to be see mapped to MIDI buttons are

• saving and loading showfiles (mapping the save and load buttons)
• DMX Dumping (to start with just being able to hit a button to bring up the dump window, But It would also be nice to be able to press a midi button and have the scene/chase mapped to that button)
  
  example use case,
  1. I have got the lights to where I want them to be,
  2. I hit a record button, followed by a button That I wish to save my chase to apc40,
  3. I then move a moving headlight to a new position,
  4. I hit record and the same button on the apc40.
     ** What I am left with is a chase with a default infinite hold, which can toggle between the two scenes when the button is pressed .
• Switching tabs via Midi input (fixture, function, show, ... etc)
• an optionally active DMX keypad that can be mapped to external control, with a default input profile set for the standard 17 key usb numpad
• The ability to pop the virtual console out onto a second screen, lock the virtual console into a set screen size, and give it the option of multiple pages without needing to use a frame.
• the option of using BPM for the speed dial rather than ms.

I have used similar functions on other lighting consoles and would like to see these ones available.

Have you read the QLC + documentation?.
A few functions you ask for are already implemented in QLC +. The virtual console can be detached from the main screen and displayed on another screen.
There is a dump function of the DMX values that can be saved to a scene or assign it to a virtual console widget.

Have you read the QLC + documentation?.

Yes, I have read through the documentation. and have been using QLC+ as my primary Lighting software for around 2 years now.

A few functions you ask for are already implemented in QLC +. The virtual console can be detached from the main screen and displayed on another screen.

Yes, You can do it manually, But having it retain the multiscreen setup after restarting qlc+ is not an option

There is a dump function of the DMX values that can be saved to a scene or assign it to a virtual console widget.

Please read the use case I wrote about, I am not talking about just the dump function, which I already know exists.

My request is about EXTENDING the existing functionality in a way that will speed up the workflow.
In my opinion, Each time You need to move from a control surface to the keyboard or mouse is time wasted. for 90% of the work that needs to be done, one shouldn't need to use the mouse or keyboard at all.