Option to have Browser window/Device palette toggle (one open at a time)? Or contextual settings

[joeyluck]

For starters, I'd really like the Browser to be dockable because it's always in the way on my display, but moving beyond that for now, I was wondering about an option to have only one window open at a time, to toggle between the Browser window and Device palette being open.

It's less common that I need both open at the same time. In fact, having them open at the same time can cause confusion. If you are browsing patches for something, and don't confirm your choice in the Browser and move on to use the Device palette and load a device into the Rack from there, if you then press Cancel or Esc from the Browser, it will also undo the device you created separately from the Device palette.

While I don't always have them both open at the same time, I almost always have one or the other open.

Browser/Device Palette Toggle

The main reason I was thinking for this flip-flop behavior would be to help with workflow and screen real estate. I use the Device palette and then I use the Browser to find a patch... Now that the Browser is in the way, I then go and close the Device palette to free up a little more screen real estate. This would take care of that automatically.

I know others have suggested an option for the Device palette to go away after loading a device, but I don't think I find that as useful? Because I'm often loading several devices at times. But I think when I choose to browse for patches, then it's clear that I'm not using the Device palette in that moment and focusing on using the Browser.

I've tried it out by pressing F3 and F9 together and what I see feels like something I'd like. This could maybe be an additional shortcut key? I was thinking I could maybe create a macro shortcut of sorts that would do that job as long as I start with one of them open and the other closed...

I know some users have wanted this "radio button" behavior when clicking on the Rack, Sequencer, Mixer buttons (having each window in full view when clicking the button). Maybe it could start with the Browser and Devices buttons?

Custom Contextual Setting for Browser

This could be handy because imagine being able to define several things that happen when calling up the Browser. For instance, maybe when calling up the Browser, you'd like to have the Rack in full view and everything else hidden. Or maybe you just choose to hide the Device palette if it's open. Maybe this is getting too advanced for what Reason might ever offer, but maybe there are better ideas that would be slick without being complicated.

[Pepin]

If the browser could be docked, then I think it might be natural to give it radio behavior with the palette when docked (like Reason 12), but it should be accessible independently when undocked imo. A radio style relationship between a panel and a floating window is a rather non-standard UI and would add to the existing confusion. You aren't always browsing immediately after dragging in a device. Suppose you click a browse icon much later. It would be strange to have the device palette hide itself at that point.

Maybe what you're really looking for is the "new devices get browse focus" option to be restored? The device palette could be automatically closed as part of that. Maybe a modifier key could be held to prevent browse focus as well, if you're creating multiple devices.

If you are browsing patches for something, and don't confirm your choice in the Browser and move on to use the Device palette and load a device into the Rack from there, if you then press Cancel or Esc from the Browser, it will also undo the device you created separately from the Device palette.

Do you mean replacing the same device for which you're browsing patches? Because if you create a device via palette elsewhere in the rack, then it remains after hitting cancel. That matches what I'd expect to happen personally.

[joeyluck]

No, I mean only showing the Browser when wanting to see the Browser and vice versa, not the Browser being shown automatically after loading a device.

I agree that if it could be docked, then having it switch in that panel space would be nice.

And yes as far as the Device palette, if you have the Browser open with device focus and replace a device using the Device palette and not the Browser, that action can easily be accidentally undone by exiting the Browser even though you've made a decision and did a thing outside of the Browser.

I had reported that wonky behavior. I definitely feel that performing an action outside of the Browser should be considered separate from the Browser. Browsing patches and not deciding on a patch is one thing, but deciding to replace a device via the Device palette is a definitive decision to move on to a new device.