Variable Opening, and Getting the HOME tab to show up on multiple screens (MAC)

When I am trying to get something working that gets to involve multiple objects, I need multiple screens to be effective. This involves undocked windows of several types - editor, workspace, figures, command. But I now find that there are no 'multiple - undocked - editor file windows', but rather only a single 'editor tabbed' window and one or more 'single' undocked' windows. And, if you are in a single window and need a 'home' tool, you must switch windows and screens.

The problem may be my own misunderstanding of the scope of the 'variables' section of the Home toolbar. In other IDEs, when you click on a variable and say 'open' variable, it shows the present state of the variable in a 'workspace' window. Not so with Matlab. In fact, whenever you ask to 'open' in a context menu on a selected variable name, MATLAB feels that you are asking to create a new file with that variable. NOPE -- I just want to open the variable which is a well known thing in the program rather than CREATE the variable which the 'New Variable' tool purports to do. The Variable Section is thus mixed up, and the context menu is mixed up. And, what I need is not there - What I want is the variable to show up in the workspace.

It is actually non-sensical to have the current 'single' undocked window rather than multiple undocked 'editor tabsets'. This is because the 'single' does not have the 'HOME' Top Tool Tab and toolbar.  The actual effect is that you can not EVER get to those toolbar functions for that file -- especially what you might want for Variables.  (It might actually be that the variables tools are not considered to be for a specific .m, but that is a slightly different issue. Why, for instance, is there no way to click on a variable in code and see it pop up in the workspace? That makes me think that 'variables' are always thought of as more like files rather than 'properties', etc.)

Does anyone have a way to get the variable to show up in the Workspace? Of course, if the variable is in an object/function that is higher up in the execution stack, it would be nice to have that stack level brought into focus in the workspace too.

D