Repository: godot
Issue: Embedded Game window stops rendering when editing other nodes in the editor
Labels: bug,platform:linuxbsd,topic:editor,usability,regression

### Tested versions

Differences between Godot 4.3 and the new embedded game window feature in Godot 4.4

### System information

Godot v4.4.beta1 - Ubuntu 22.04.5 LTS 22.04 on X11 - X11 display driver, Multi-window, 2 monitors - OpenGL 3 (Compatibility) - AMD Radeon RX 6600 (navi23, LLVM 15.0.7, DRM 3.57, 6.8.0-51-generic) - AMD Ryzen 7 5700X 8-Core Processor (16 threads)

### Issue description

Godot4.3 works great already for gaming while editing it at the same time. I run the game, and then 'windows key + tab' over to the editor to make changes and see it in real time. I was curious if the embedded game window would make this even better somehow but certain what the added functionality would be.

In Godot 4.4 beta, when running the game, it pops up in the new window, on my second screen. If i tab over to the editor to make a change to any nodes, it detects i'm now looking at a specific object , or script, and not the game anymore and so stops rendering the game in the second window. This is very  frustrating. I'd normally pop over to the editor to adjust a Directional Light, or Environment Fog, and see it in real time in the game, but the embeded view stops rendering so now i have to tweak, and then tab back, and tweak and tab back. And it's a lot more work to see changes in real time.

I can't seem to find a settting to have it 'always on' even when not on that tab, or revert back to a classic mode or something. 

EDIT:
![Image](https://github.com/user-attachments/assets/08b7dbd4-db63-4a47-9a39-aa313b38621f)

Aha! So these are the settings to go back to a classic mode. The wording on both is a little odd. Since Embed and Docked can have similar meanings and these two settings next to each other aren't clear because of it. I was going to close the ticket but instead i'll edit it to reflect the wording issue, and that when floating the game workspace, it should keep rendering even when editing other things. That's seems the whole reason to make it a floating window no?

So wording wise:

Enabling a bool for "_Make Game Floating on next play_" is the most curious to me. I'd think this wording better:
"_Dock Game Window_"  (Enable the bool to dock, and disable to make floating, inverse of what is current here)

And the other setting "Embed Game on next play" add confusion since embed and dock have similar ideas. I was unsure what it meant since it sounds like docking/floating, the window and isn't clear it means it's going to actually enable or disabled in-editor game workspace.

Perhaps better wording there too:
"_Enable in-editor game workspace_" (disable to run externally)

### Steps to reproduce

I start any game running using the "embeded game on next play" and "make floating" settings enabled.
See it running on your second monitor
Tab back over to the editor.
See the game stop rendering the second you go to edit anything.
Click back to the game and see it come back.



### Minimal reproduction project (MRP)

Load a project.
Start the game
Move the game to a second scree or even just split your screen into section.

Click on any node in the editor. the game stops rendering, swaps to 3D, Script, 2D etc, tabs, and you can't make realtime edits and see them in game.