Move collection visibility panel from popover to sidebar panel #63527

Closed
opened 2019-04-12 10:13:18 +02:00 by Brecht Van Lommel · 21 comments

The popover is not very popular, instead it can go in the sidebar in its own Collections tab. This way animators can have it permanently open for example and don't need an outliner.

The popover is not very popular, instead it can go in the sidebar in its own Collections tab. This way animators can have it permanently open for example and don't need an outliner.
Dalai Felinto was assigned by Brecht Van Lommel 2019-04-12 10:13:18 +02:00
Author
Owner

Added subscriber: @brecht

Added subscriber: @brecht
Brecht Van Lommel changed title from Move collection visibility panel from popover to sidebar to Move collection visibility panel from popover to sidebar panel 2019-04-12 10:13:32 +02:00

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

We could do the same with this panel too I think:

Screenshot 2019-04-12 at 10.24.29.png

We could do the same with this panel too I think: ![Screenshot 2019-04-12 at 10.24.29.png](https://archive.blender.org/developer/F6934210/Screenshot_2019-04-12_at_10.24.29.png)

Added subscriber: @LucianoMunoz

Added subscriber: @LucianoMunoz

no, please, that panel is super useful in production! (the object types visibility)

the only thing i'd change aboout it it's it shouldnt affect the objects visibility togleability in the outliner, it should be something superficial only for the viewoort, its a restriction so you dont move things my mistake or to be able to see what you need to see, but you dont want it changing properties.
Also if it's local to a view it's great for filtering out whatever you need to see in one view or other.

no, please, that panel is super useful in production! (the object types visibility) the only thing i'd change aboout it it's it shouldnt affect the objects visibility togleability in the outliner, it should be something superficial only for the viewoort, its a restriction so you dont move things my mistake or to be able to see what you need to see, but you dont want it changing properties. Also if it's local to a view it's great for filtering out whatever you need to see in one view or other.

Added subscriber: @lastrodamo

Added subscriber: @lastrodamo

Added subscriber: @ideasman42

Added subscriber: @ideasman42

In #63527#659189, @WilliamReynish wrote:
We could do the same with this panel too I think:

Screenshot 2019-04-12 at 10.24.29.png

This would remove the icon which currently changes based on the options inside the popover.

This means you wouldn't know at a glance if you have any object types hidden or un-selectable.

Since there are (at least) two ways to make something hidden / un-selectable - I wanted to avoid users having to search in a collapsed panel/region for eg, to find their object type can't be selected.


Would prefer design tasks don't add in unrelated changes in replies too, it makes things hard to follow and adds noise (anyone wanted to read about the original task now needs to wade though unrelated discussion).

> In #63527#659189, @WilliamReynish wrote: > We could do the same with this panel too I think: > > ![Screenshot 2019-04-12 at 10.24.29.png](https://archive.blender.org/developer/F6934210/Screenshot_2019-04-12_at_10.24.29.png) This would remove the icon which currently changes based on the options inside the popover. This means you wouldn't know at a glance if you have any object types hidden or un-selectable. Since there are (at least) two ways to make something hidden / un-selectable - I wanted to avoid users having to search in a collapsed panel/region for eg, to find their object type can't be selected. ---- Would prefer design tasks don't add in unrelated changes in replies too, it makes things hard to follow and adds noise (anyone wanted to read about the original task now needs to wade though unrelated discussion).

Added subscriber: @1D_Inc

Added subscriber: @1D_Inc

I can hardly imagine how you will do it for 2357 collections in scene.
Maybe by creating special outliner for outliner?
That will be actually interesting to see...

I can hardly imagine how you will do it for 2357 collections in scene. Maybe by creating special outliner for outliner? That will be actually interesting to see...
Author
Owner

You wouldn't use this to manage that many collections. It's more if you have a limited number of top level collections that you switch between often.

You wouldn't use this to manage that many collections. It's more if you have a limited number of top level collections that you switch between often.

In #63527#660247, @brecht wrote:
You wouldn't use this to manage that many collections. It's more if you have a limited number of top level collections that you switch between often.

You've got me =) Sounds like proper QCD system atop Collections.
https://devtalk.blender.org/t/layers-maniphest/6578/32?u=1d_inc

> In #63527#660247, @brecht wrote: > You wouldn't use this to manage that many collections. It's more if you have a limited number of top level collections that you switch between often. You've got me =) Sounds like proper QCD system atop Collections. https://devtalk.blender.org/t/layers-maniphest/6578/32?u=1d_inc
Author
Owner

I think this should be in its own category tab? Right now it's expanded by default along with the other panels. If you've got lots of collections this pushes down the annotations a lot, and is not ideal for performance either.

I think this should be in its own category tab? Right now it's expanded by default along with the other panels. If you've got lots of collections this pushes down the annotations a lot, and is not ideal for performance either.

@brecht Not sure about the category - what category should it be then?

Certainly I can collapse by default no problem.

@brecht Not sure about the category - what category should it be then? Certainly I can collapse by default no problem.

@WilliamReynish It could be "Collections", or "Visibility". If we are talking about a production scene, you can have enough collections to fill most of the vertical space of the viewport.

@WilliamReynish It could be "Collections", or "Visibility". If we are talking about a production scene, you can have enough collections to fill most of the vertical space of the viewport.

In #63527#661931, @dfelinto wrote:
@WilliamReynish It could be "Collections", or "Visibility".

Well, there are a lot of "Collections" and "Visibilities" over interface already)

If we are talking about a production scene, you can have enough collections to fill most of the vertical space of the viewport.

Easily.
Does it mean, it should be the rightmost button on a panel?

> In #63527#661931, @dfelinto wrote: > @WilliamReynish It could be "Collections", or "Visibility". Well, there are a lot of "Collections" and "Visibilities" over interface already) > If we are talking about a production scene, you can have enough collections to fill most of the vertical space of the viewport. Easily. Does it mean, it should be the rightmost button on a panel?
Member

Added subscriber: @JulienKaspar

Added subscriber: @JulienKaspar
Member

Added subscriber: @jendrzych

Added subscriber: @jendrzych
Member

Removed subscriber: @jendrzych

Removed subscriber: @jendrzych
Author
Owner

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Author
Owner

I think we can consider this resolved now.

I think we can consider this resolved now.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#63527
No description provided.