My quick search didn't come up with this exact idea.
To me it seems like a good idea to be able to use midi controls during programming.
Especially for pan/tilt configuration using a midi controller's encoders. Either using 1 or 2(16bit) for each, pan and tilt.
The simplest implementation I could think of would be to add the settings to the input profile of a midi device.
One option would be adding "program input" 1->n with options for fader/encoder/poti and these corresponding to the channels activated in a scene.
For rgb matrices R/G/B, for EFX width/height/X&Y offset/rotation/start offset.
Another option would be to assign the midi controller controls to certain fixed parameters like pan/tilt, dimmer, r/g/b, etc.
Additionally adding fade in/fade out/hold may come in useful, too.
So depending on a midi controller's available controls one would be able to make use of them during programming.
Maybe even making more or less the whole of qlc+ available for midi controls:
-Enabling/disabling preview (especially for rgb matricies and efx)
-new scene/chaser/etc.
-switching between windows (fixtures/functions/etc.), although this may be obsolete/less needed due to the new workflow in qlc+5?
I could see myself using something like my apc40mk2 during programming and it being used for lots of the programming.
But even a smaller controller like a Novation LaunchControl would come in handy.
[edit]: this thread from last year discusses the basic idea as well and puts it off to qlc+5. To me definitely worth getting further in to. http://www.qlcplus.org/forum/viewtopic. ... it=encoder
Q Light Controller+
Official forums of the QLC+ project