I don’t know if it’s a bad thing - I don’t know the use case and I don’t know what problem would actually be solved because, as you yourself observed, you are “making life complicated”
Absolutely. 
I always repeat myself - I’m probably one of the few who uses GP just for the midi. So my expectations are much different than “normal” users. So I just have to make peace with some things, I guess.
Thanks for all the suggestions and answers, like always, GP community ftw.
That is fine but I still don’t understand why mapping a widget to a message is any more onerous or time consuming than, for example, just selecting an alias defined in the rig manager for the widget
That’s just a drop down box and you just select the mapping
I’ll be honest. Never understood how rig manager works and why I need it. Whenever I tried something with it I found that it can’t do what I needed. I’ll see for this situation if it helps. Thanks.
What were you trying to do?
Here for example are three knobs defined with names (aka aliases) in the Rig Manager and they have been mapped once to separate CC messages
To map it, just go to the MIDI section, click the dropdown button and select the desired knob by its alias name
Now it’s mapped and can be controlled from your hardware. Do this on all your rackspaces, no MIDI learning required.
Bonus - if you get a controller that uses different MIDI messages for its knobs, just learn those new messages in the Rig Manager and your rackspaces will just continue to work without any changes
You are not making things complicated, for me controlling local widgets from global rack space is the critical thing, mapping controllers to widgets in each local rack space is silly and inefficient.
Unfortunately, GP doesn’t have a way to do it, the solution for grouping local and global widgets work the other way around for whatever reason I could never fully understand.
I made a solution for this with scripting, but it is complicated. Use X-Touch Mini to control everything (gig, scripts, panel & overlay templates included)
I meant that in the context of what he is trying to do, it didn’t sound like he even needs the global rackspace.
But I just realized from your response that we have been talking cross purposes.
He doesn’t mean widget grouping….he means widget linking and the idea would be to have widgets with the same link apply across the global rackspace and the current active rackspace.
That is actually an intriguing idea and if we had invented widget linking before we created global parameters, we might have never needed global parameters.
There is other work ongoing with both linking and with the relationship between widgets in the global rackspace and local rackspaces but we will look into this idea.
Which is exactly whay I was trying to achieve with my megaton of scripting, and we had like a dozen discussions about this.
Global parameters in GP are a very strange thing as they are related only to the “global rackspace” and therefore aren’t really global.
Yeah, but somehow I never grasped that you were talking specifically about the notion of widget links working between two different rackspaces (global and local). It’s obvious now, but wasn’t at the time.
It’s a very good idea.
1 Like
I’m glad the topic evolved, which I didn’t expect.
First, thank you dhj for idea for the Rig Manager, sure I’ll try to do that.
Then, thank you vangrieg for making me less lonely. 
Yes, linking widget from global space to a local one is what I need. My initial idea was trying to configure two different midi sources to control same operation - for example, in global midi settings you can address only one midi source for “next song part”. I wanted to have a possibility to change song part with pedal switch AND pad on the master keyboard. Global rack space would help in that case too, if I would be able to link it to a widget which is doing the “next song part”. Then my idea expanded to mapping external controllers to virtual counterpart in GP’s global rackspace and simply link it to different things in local rackspaces.
Anyway, rig manager should be a workaround. The Parameter tutorial skipped the step where I have to create the same mixer I already have in the local rackspace, when I did that every other step makes sense, but overal not so much. What’s the point of the global parameters if I have to create ALL the same widgets and blocks in the wire page to connect it to a local rack. So, the rig manager is the way to go for me.
Thanks everyone!
I think we see global rackspace differently. In my mind global rackspace is a part of local rackspace. For me It’s just one more unit panel within the each rackspace which is always there. It just cross my mind when you said between “DIFFERENT rack spaces”. Maybe I’m wrong but for me global rackspace is not different, it’s the same rackspace but the unit panel that’s repeating in every rackspace. Hope I’m clear enough.
edit: this is reply to dhj’s last post.
Different local rackspaces
I thought you meant two as in one global and one local.
The global rackspace is always available (hence “global”)
There is only one local rackspace active at a time.
Exactly, so one local and one global rackspace is active at one time. So you said “between two different rackspaces”, what you meant by that? For me they are not different, they are a part of one active rackspace (local + global), the difference is just the local part is exchangeable by song or song part, and global part is not - it’s always there. It’s exactly what I have “in real life”, the switch pedal which is always, well, switch pedal, and programs, effects and VST or whatever which is changeable. As I would program the switch pedal to do different things on my keyboard workstation (while not using GP), same would be to use global rack space to link to different things in rackspaces. This is just for the example, the options are countless if the global rack space had more possibility in connecting with the local ones. At least in my book. What I see now is that global rack space is restricted to using one layer of piano in each song (I exaggerate), which is not so many situation like that.