Forgot to add, debugged this with @Campbell Barton (campbellbarton). I wouldn't just commit such a change in makesdna without clearance ;)

Managing the workspaces of the workspaces.blend is actually something I hoped to allow through the new Blender settings design, see T54115.

For the records, I agree Ctrl + Q → Enter should still work, I can have a look at it after the code quest.

Committed rB77e9193c2317. Thanks @Aleksandr Zinovev (raa)!

Aaand pushed. Thanks @Diego Gangl (januz)!

Agree, better to use a checkbox here to be clear. Don't think the drawing is clear enough really.

Am generally a bit wary of such changes in such vital functions, but think this is fine and worth trying. Only briefly tested though ;)

Don't think there's a nice way to support displaying the keymap item string in the tooltip. Only if we added support for dynamically generated operator descriptions/tooltips (which in fact might be useful to have). So for me this is good to go, even if I'd really like to have the tooltip thing working (this is a general issue in Blender though).

Although it doesn't completely resolve what's reported here, rB72e5082b6757e does relating changes. Would still be nice to have proper "focus" support.

Almost there! Functionality wise this seems to work just fine now. Just have a little more nit picking ;)

Was checking if we can do this more generically, e.g. in ui_block_bounds_calc_text. Doesn't seem to be possible in a nice way though, so think this approach is fine.

Fixed by commit rB357b72e0a7d4a.

Committed rB60712d12eb89f. Thanks!

This finally landed in master! Committed rB60712d12eb89f.

Agree that "workspaces" isn't the best term by now, but "Editors" sounds ambiguous too. Everything in this list is an editor, most even have the term in their name. Maybe something like "Main" or "General"? Or "Interaction"/"Interactive" since these are the main editors to interact with data visually. Or something like "Graphics"?

Doubt they are related, this issue happens within the draw-manager.

All points should be addressed now. I kept the system "General" section (contains all system settings), think that's fine, even for an initial commit to blender2.8.

• Address most minor points from review
• Revert some rather experimental changes

Committed rB41b38c5f75b3 to avoid misleading users like it happened here.

In D3088#73065, @Brecht Van Lommel (brecht) wrote:

The unfortunate but simple answer to this is: It's not supported on Windows. When I reviewed (well, more like continued coding) the patch for IME support on Windows, cases like console and text objects were way too broken. Hence, we decided to not add these changes. You should still be able to input Japanese characters using the redo-panel though:

Bah... I'm a moron :| View-layers belong to the scene data-block, so we can read them just fine when linking. NVM then, this is not an issue...

Yes, seems like we can use names/identifiers. I can do this if you're not on it already?

I think I'll actually go ahead and start working on this in the blender2.8 branch, just like @Brecht Van Lommel (brecht) suggested. There don't seem to be any bigger objections against the proposed changes :)

It's not a parent or sub-task of this, but T54115 is definitely related to the workspace work.
Basically it should allow us to create a proper UI for editing the workspace settings (add-on and keymap overrides) and the workspace configuration file (like adding/removing workspaces).

In T54115#485386, @David (activemotionpictures) wrote:

Could this be a good time to propose a NEW SPLASH screen? to better simplify the first user enounter with the software?

In T54115#485326, @Joshua Leung (aligorith) wrote: