In T69819#1173214, @Harley Acheson (harley) wrote:

@Ray Mairlot (madog) - I don't know whether I am missing something...Having two main windows might fix this (I haven't tried)

You should give that a try to see if that helps. "Window / New Window" versus "Window / New Main Window" give quite different results from each other now. Each main window controlling children, with separate grouping on taskbar, etc.

I don't know whether I am missing something or maybe what I'm about to bring up is already on the agenda, but having just started using Blender 3.0 with a dual screen setup (one main window and one secondary/regular window), having used blender for years with multiple windows on multiple monitors, I am finding the new 'child' window feature is now severely interfering with how I normally work.

@Philipp Oeser (lichtwerk) All working fine now :)

I think the bug here is less that it doesn't have a shortcut by default and more that there is an operator that isn't present in any of the 3D view menus and can only be found by the search menu.

@Brecht Van Lommel (brecht) Ah, thanks. I had been using two main windows in order to have the File, Edit, View.. etc. menus on both screens as this is the setup I had in 2.79, but I see now that in addition to scenes, workspaces also sync when using a main and secondary window so I will switch to using this.

Hi, I'm just wondering why the 'Use Global Scene' option was removed and whether it will return? I use multiple monitors and used it to make sure all windows were using the same scene to prevent editing a material in the shader editor on one window and wondering why the other window with the 3D view isn't updating, only to find one window is set to a different scene.

I see @Christian Brinkmann (poor) suggested the Render Border as good candidate for widgetification (+1 from me), but I think maybe you missed this suggestion @Campbell Barton (campbellbarton)?

Hi. Seeing as it was asked, I just thought I would chip in and say, yes, there is another add-on that does this (though it works on a 0-1 scale instead of pixels), my 'Animated Render Border' add-on: https://blendermarket.com/products/animated-render-border/ .

The correct tagging of information allows said information to be accurately searched, which from a user perspective is important to be able to find existing bugs to prevent reporting duplicates. Personally, I would also think it's important from a developer perspective to make sure the ever important bug list is not populated with things which aren't bugs, but then I'm not a developer. I'd say this sounds more like a task, but if you're saying it's a bug, fair enough.

Is this meant to be tagged as a bug?

I notice that this and a few other documentation tasks are of type 'Bug', but shouldn't they be 'Design' when they are about discussing changes?

@Sergey Sharybin (sergey) Ok, thanks, I thought it may be a dependency graph issue. I just thought it was weird that 'emitter' particles updated their colour, but 'hair' didn't.

@Philipp Oeser (lichtwerk) Yes, I understand I can access the points and calculate the bounding box manually, the main point of this report was to say that if the bounding box option is available I expect it to update and if 'bound_box' is available in the api, I expect that to return correct values (which I also expect for the other object types I mentioned).

@perfection cat (sindra1961) I'm not sure what I should be looking at on that page.

Meant 2.75a.

Yep, changed to US keyboard language and it worked.

As I said in my original report, I tried this on a separate windows 8.1 machine. I have since tested:

Ok, so I just found that if I press the apostrophe key ( ' on the same key as the @ symbol) I can toggle all the layers
(I'm using a standard UK qwerty keyboard). I was under the impression that it is the backtick key ( ` ) commonly found above the 'tab' key and to the left of the '1' key that should be toggling the layers.

This may be a similar situation to what @Karja Krähwald (karja) said above, but particularly when modelling wheels/tire tread it is necessary to merge the beginning and end of the tire to create a complete circle.

@Campbell Barton (campbellbarton) Ok, thanks for clearing up how it works, that helps.

Ah sorry, forgot this:

Blend File: