Closing since this isn't a bug.

Having no active item is a idiosyncrasy I have found before in previous versions of Blender, never been an actual problem, but is curious case to tackle.
Here is a more complete laydown of all the distinct cases I could think of, hope it helps you get this right.

In T60557#601014, @William Reynish (billreynish) wrote:

Sounds good to me! It will make it a lot less likely to end in the bad state of having active object not be selected, or no active object at all.

Sounds good to me! It will make it a lot less likely to end in the bad state of having active object not be selected, or no active object at all.

Ok, let's do it. :D

Overall I agree - it's just that the active object is quite important. The active object is the one whose properties you see in the Properties Editor. If it makes a random one active, you'll see a random set of properties here. IMO it's slightly nicer, although admittedly still weak, if we at least try and do something more deterministic, such as the object that was closest when starting or ending the box selection, if the active object is outside the selection box.

Right, I don't want it to be repeatable, because then users start relying on it ;D If someone has a perfect plan on how to make it very predictable, the behavior can be changed later on.
Also if you want to merge/join, the user should be explicit anyway by selecting the new active object individually.

We could do that - but it would indeed be random, which is not nice. If you then do a merge or join, it will happen relative to a completely random object in your scene. The more deterministic solutions are also weak, but at least repeatable.

I think trying to be smart like that is the wrong approach.

Yes, we could do that, but as you say, there's no obvious solution when box selecting multiple objects. We could try and do something smart, like making active the one that is closest to the starting point of the box selection, or if an object is under the cursor when you let go. Something like that.

Right, we could at least make it so that when only one vertex/object is selected with box/circle/lasso select, this will be the new active vertex/object.
Not sure how to handle the case when multiple objects are selected..

Technically I would say it's not a bug, but a design issue to do with the fact that we even have the concept of active vs selected in Blender, which can be entirely different.

We have the same problem elsewhere. With the box select tool, you can easily end up in a situation where the active object is not selected, or there is no active object at all. Many tools and commands in Blender act on the active object.

First I thought that I might have introduced this bug in rBa0df26f00. However, that sees unrelated.

This change matches what we did elsewhere to make the checkboxes work correctly, so the diff should be correct. @Brecht Van Lommel (brecht) can confirm.

Hi! Thanks for the poke, I missed this one.

Resolved by D3997: Node Resizing Hit Area.

@Pablo Vazquez (pablovazquez) what do you think?
This change by @Anton Stötzer (blendermusic) looks good to me. Can we get it merged?
Or are there other proposals like using an icon that changes between grey and red prohibition circle (think no smoking or ghostbusters)?
Grey for "mute" off (modifier is active)... Red for "muted" (modifier disabled).

@Brecht Van Lommel (brecht): Can you check on this? Thanks :)

Ah, I see. That'll do it, thanks!

In T54963#593809, @William Reynish (billreynish) wrote:

@Cezary Szadejko (cez): It's still alive but still waiting for issues to be solved with left click described here: T57918. Now that left click is enabled by default, it's paramount that we tackle these remaining issues anyway, and that will also pave the way for keymaps such as this one.

To have two windows showing different scenes use "New Main Window" menu item.

In T58969#598369, @Hadrien Brissaud (hadrien) wrote:

This should probably be reversed to match current selection paradigm :

• shift to select another element
• ctrl to select path

This keyboard is mandatory for the new blender.
Your work on this is fantastic but this can't be without work on snapping too (so removing the 3d pointer). Please don't forget that

In T60403#599019, @Brendon Murphy (meta-androcto) wrote:

hi, Addons are specifically designed to interfere as little as possible with Blender default keymaps. They are also iirc, loaded at start up. You are using custom keymaps which can fall outside the scope of addons design and default key mappings at the moment. I feel that what you are requesting is outside of addons/keymap current design. To get around this you can edit the individual files that give you trouble with your custom keymap. I'm not sure this is a bug or a feature request or simply a limitation of the current design and the way things work.
A more knowledgeable blender developer may correct me if I'm wrong here.

hi, Addons are specifically designed to interfere as little as possible with Blender default keymaps. They are also iirc, loaded at start up. You are using custom keymaps which can fall outside the scope of addons design and default key mappings at the moment. I feel that what you are requesting is outside of addons/keymap current design. To get around this you can edit the individual files that give you trouble with your custom keymap. I'm not sure this is a bug or a feature request or simply a limitation of the current design and the way things work.
A more knowledgeable blender developer may correct me if I'm wrong here.

Removing old 2.8 config fixed problem.
Thanks.

It's correct in the default startup file, probably you have saved your own startup file which still has the old workspace.

This is still broken.
UV workspace has the image editor not the UV editor and to make matters worse they look the same. I had no idea why the UV editor was not working at first.
:-)
Fight the burn out! You guys are almost there!

I have this problem. If I go into fullscreen and then open Preferences, the entire interface blinks black for a split second and then opens the Preferences window behind the main one. However, in terms of interaction logic, the interface still 'thinks' Preferences is in focus - I can edit values and hit buttons even though it is rendered behind the main window, and any buttons I want to press on the main window are blocked.

@Christopher Anderssarian (Christopher_Anderssarian) disabling V-sync did solve issue, that refresh rate depends on open panels.

In T60336#598496, @Richard Antalik (ISS) wrote:

Disabling V-sync solved this.

@Richard Antalik (ISS) What did it solve?
Your actual description says:

UI refresh rate varies a lot depending on open panels, even with constant load

Did disabling Vertical refresh sync fix this? Because I have 'Wait for Vertical Refresh' disabled by default in My Radeon Settings and I show your reported issue.

I have noticed, that when you create new file from video editing template, render result is shown in new window, sequencer drawing code is not executed.

Thank you for explanation.
Disabling V-sync solved this.

Please try the latest Blender build, this was solved some time ago.

2: Select all items in-between when holding shift / select individual items by holding Ctrl.
When holding shift to select multiple items, we can select all the items in between.
Users can then use Ctrl to select individual items without the ones in between.