- User Since
- Dec 12 2013, 11:11 PM (218 w, 5 d)
Thu, Feb 1
Mon, Jan 29
This raises the question on how we should handle view-layers when linking scenes. Should we link view-layers with them? If so how can we do this (since view-layers aren't IDs)?
I don't recall if we ever discussed this.
Jan 22 2018
Jan 12 2018
My point is that storing the Scene ID in there is not what we should do. We'll probably need to change how this pointer is used in future, so that we can uniquely identify the TreeStoreElem when recreating its TreeElement.
Really, this concern is about all changes done to how TreeStoreElem.id works. And it worries me that we now make more changes assuming that this pointer contains the scene ID.
Hence me suggesting to avoid further changes in this regards. Just leave it as is and I'll try to fix the actual root of all these issues as soon as I can.
Jan 11 2018
No, we really shouldn't do that. This may fix the issue of unwanted collapsing, but just gets us deeper and deeper into a rabbit hole of hacks.
This only works because we currently store the scene ID in the TreeStoreElem of collections - which we shouldn't do either. Like I mentioned earlier in IRC, doing so just moves the bugs to a different place. E.g. messed up highlighting of elements after undoing a deletion. And this is just a rather harmless symptom of potentially not so harmless issues in data.
Hmm, would rather avoid such an option. Ideally we'd make the entire area splitting UI more intuitive. But until that is done, templates can just unset the AZone "shortcuts" (Handle Area Action Zones).
Jan 10 2018
I know you plan to do further changes to this, but just quickly went over code and noticed some rough edges that I don't want to end up in master/blender2.8 ;)
Dec 27 2017
Dec 26 2017
Dec 23 2017
- Fix workspace mode changes to edit-mode when adding objects
- Fix possible issues when changing active object
I will add this as separate patch so we can test which behavior works best.
Dec 22 2017
Dec 19 2017
Dec 15 2017
Submitted experimental version of my previous comment, D2965. This is just for testing the idea really. It is the most feasible solution I can see (design and implementation wise).
Dec 7 2017
On further discussion with @Dalai Felinto (dfelinto), he proposed doing things a bit differently:
- Workspace stores a mode and tries to keep it active.
- Object mode is used as fallback (e.g. when activating an object that doesn't support the workspace mode)
- Pressing ⇥ (tab) would toggle between the workspace mode and object mode, as opposed to toggling edit mode.
Or in other words, the workspace mode would be like a primary mode, with the object mode as secondary one for backup.
I'm not a fan of using colors to indicate overridden properties. It starts getting really hard to track which colors mean what: We have yellow for keyframed values, green for interpolated values, magenta for driven values, blue for multi-editing. And now we add cyan for overridden values.
We also shouldn't forget color-blind people. If we only use colors to communicate certain information, color-blind people may not be able to catch this info.
Maybe this topic should be addressed more broadly though.
Dec 6 2017
Dec 2 2017
Dec 1 2017
Nov 30 2017
While this is technically an option, it's probably not a useful behavior for users.
I guess in most cases they would simply end up in object mode when switching workspaces. Say a user has a workspace for animation, each time she'd switch to it (from a non pose mode workspace) she had to select an armature first, then change the workspace. Or change the workspace (Blender switches to object mode), then select the armature, then manually enter pose mode.
It would only work in few cases.
Nov 28 2017
Hey, great to hear you're making progress! You're proposed solution is pretty fine with me. In fact I had the same in mind but wanted you to get there yourself ;) Who knows, maybe you would've found a much smarter solution than I did!
That said, I still see two cases to cover:
- What if collections 3 & 6 are selected (from your example with 8 collections)?
- What if the first collection is selected?
Nov 27 2017
Nov 26 2017
Hey, this is an old task, pretty much forgot about it :S
With Blender 2.8 we plan to introduce a new 'workspace' concept, combined with a new template system. See https://wiki.blender.org/index.php/Dev:2.8/UI/Workshop_Writeup#Workspaces. Basically, workspaces are there for users to organize the UI for different tasks they are doing, templates for the different kinds of users or the different contexts they use Blender in.
Everything in that document is somehow related to workflows, but workspaces & templates are the most important ones for this task.
Nov 25 2017
Nov 24 2017
@Sergey Sharybin (sergey) I heard you're quite against the idea of syncing the workspace mode with the object mode. Mind explaining why exactly? :)
Although this seems totally easy to solve, there are some things to consider:
Should we only update selection? Wouldn't users expect to see the active collection updated as well, so active & selection stay mostly in sync? Which collections are activated and/or selected when deleting multiple collections? What if there are unselected ones in-between selected ones?
It boils down to a single question: Which collection(s) is/are selected and which one is the active one after deleting collections in any way?
@Danrae Pray (spockTheGray) hey, have you already investigated this? Asking because I think this should be done carefully.
We could just fix this bug, however there are quite some glitches with collapsing of collections in the outliner. So I'd prefer a better solution for this in general which would also fix this issue. Finding a good solution may require good knowledge of outliner, file read/write and versioning code. Feel free to go ahead if you're up for the challenge, otherwise I'd pick it up again.
Nov 23 2017
- Cleanup: Update comments
- Fix issues parsing BPY defined props, add BPY documentation for tags
Nov 20 2017
Nov 19 2017
Nov 18 2017
Updated the task description to show the answers which we agree on (at least from what I can tell).
Hey @Vuk Gardašević (lijenstina), let me finally get back to your proposal. In short, it doesn't really convince me ;)