Hi Everyone,
Would there be any wisdom/use in making an option to have key-mappings inside frames with multiple pages, local to only the current page?
For instance: If I'm in page 1 of a frame... and have a button mapped to the letter "A" - which loads, for example "Scene 1 - ALL BLUE" - and then on page 2, in which I also have a button mapped to the letter "A" - which loads "Scene 2 - ALL RED" - it would be great if the button activated would depend on the page I was on. On page 1 - "A" would get me all blue... If page 2 were open - 'A" would get me all red.
I do understand that having "Global" key mappings is really handy as well - but I wonder if it would be difficult to make some key mappings be context sensitive. It would greatly expand the "library" of things that could be done on a keyboard (pedal board in my case) with few keys/buttons. Perhaps key mappings would be considered "page specific" unless a "Global" check box were selected - making it so that a particular button could be accessed from a key *anywhere* in the virtual console?
I think it would be similar to the behavior of old boards like the NSI MLC-16. Allowing you to access bunches of key triggered sequences and functions with limited key real estate.
Thoughts?
Scott
Global vs Page Specific key mappings
Hi Massimo,
I would like to bring this topic back up. It is a show stopper, it really is.
I created a frame with 3 pages so far. Each button has it Combination Key to start/stop the function.
The problem is if I press 'L' to start the function on page 1, it start functions on page 2 & 3 at the same time.
Please I don't know if that is a Midi issue as well as I have not tried it yet.
Thanks and just updated to 4.8.1 so working
I would like to bring this topic back up. It is a show stopper, it really is.
I created a frame with 3 pages so far. Each button has it Combination Key to start/stop the function.
The problem is if I press 'L' to start the function on page 1, it start functions on page 2 & 3 at the same time.
Please I don't know if that is a Midi issue as well as I have not tried it yet.
Thanks and just updated to 4.8.1 so working
Jimmy, this has been fixed since QLC+ 4.8.0 (see release notes)
If it still doesn't work, then there must be something else.
By the way, there's version 4.8.2...
If it still doesn't work, then there must be something else.
By the way, there's version 4.8.2...
Hey Massimo,
Figured it out, its a small bug. When you start the project/show the widget pages are not set so if you select using a key combination it activates all that use that key. Once you change the page on the widget that widget works properly. Test file attached.
Yea I updated to 4.8.2 and loaded it tonight on OSX and my RPi.
Thanks
Figured it out, its a small bug. When you start the project/show the widget pages are not set so if you select using a key combination it activates all that use that key. Once you change the page on the widget that widget works properly. Test file attached.
Yea I updated to 4.8.2 and loaded it tonight on OSX and my RPi.
Thanks
- Attachments
-
- test.qxw
- (15.05 KiB) Downloaded 24 times