Blender enthusiast, programmer, UI/UX enthusiast, and all-around good fella.
- User Since
- Nov 8 2014, 5:14 AM (294 w, 5 d)
I updated the diff for LayerCollection IDs. It now works for all View Layers and is much closer to being functionally complete, whether the main devs are happy with my implementation, well, we'll just have to wait and see :P
And I found a bug in the Collection Manager while I was at it ;)
For more info see https://developer.blender.org/D8024
I've updated this with full support of View Layers. Hopefully, everything should
stay properly synced and unique. I had to switch to a different method to handle
View Layers, and it unfortunately adds in more global variables, and more loops over
Mon, Jun 29
What I was thinking, is that if you want to focus on a branch then numerating the others just adds clutter, but I could be totally wrong. Anyway, I'll put out a test with just the non-hierarchical depth first ordering and see how people respond to it, and maybe a limit to branch function, and we'll go from there.
Sat, Jun 27
This numeration pattern affects collections on higher levels as well, so it may not always be desired. I'd like to first see if anyone on the blender artists thread has any objections before changing it. Another thing which might help is if I add a "limit to branch" function on shift (so only the collection designated 1 and its children are numerated) for both breadth first and whatever depth stuff we decide on.
Fri, Jun 26
Okay, yep, that ordering pattern is possible.
So you want to replace depth first ordering with non-hierarchical? I'm not sure it's a good idea to replace it. I think it would be a better idea to add it as an option and use a new hotkey (Ctrl+Shift?), but regardless, I think it might be possible. I'll have to experiment a bit.
Thu, Jun 25
- Added an option to align local rtos and operators to the right.
- Added a line separator between each collection.
- Added a depth first renumber option.
@Paul Kotelevets (1D_Inc) Done. I did that in the blenderartists thread, but forgot about doing it here. Thanks for reminding me.
Wed, Jun 24
Sat, Jun 20
Thu, Jun 18
@Bastien Montagne (mont29) Not sure if you get automatically notified of new comments, but in case you don't I just want to mention that I've responded.
Actually, since the session_uuid is tied to the Collection, and not the LayerCollection it won't work as a unique identifier (because of internally linked collections). So to make that work LayerCollections would have to be made into ID data-blocks.
Upon further consideration, I'm starting to think that LayerCollection ids should be unique to each view layer because properties of the layer collection (exclude, hide, etc.) are unique to each view layer.
Name collisions can also happen within the same blend file for LayerCollections because of their ability to be linked internally. When you drag and drop a LayerCollection with ctrl it creates a new LayerCollection at a different point in the tree with the same name (and of course it points to the same collection). Besides solving name collisions, having a static unique id for each LayerCollection would vastly simplify storing references to them (the references wouldn't need to be updated and it would avoid edge cases where it's impossible to update correctly when two LayerCollections under the same parent swap names on a rename).
Wed, Jun 17
@Germano Cavalcante (mano-wii) & @brect Don't know if this is relevant here, but I remember there was a bug or discussion about never ending modal operators and autosave a while back (I think the blenderkit addon uses one).
Mon, Jun 15
I've started a patch for LayerCollection IDs.
@Nathan Craddock (Zachman) I know you're busy with GSOC, but since this will go somewhere and it relates to the outliner I thought I'd mention it to you.
Thu, Jun 11
Better this will be a known issue until a unique identifier appears.
@Nathan Craddock (Zachman) Interesting video, however I find it to be a bit visually confusing and inconsistent. I know it's still early days, but here are a couple of thoughts.
Tue, Jun 9
@Paul Kotelevets (1D_Inc) Here is a test fix for displaying linked collections. It doesn't support saving and loading QCD slots, but should hopefully be as stable in everything else as the current release. During testing, I found that both it and the released version have a bug where QCD slots can swap collections when renaming and undo/redoing. This bug is unsolvable without actual unique ids on LayerCollections. Depending on whether addon fixes are allowed in 2.83 updates, I may be able to add it to the 2.83.1 release, but moving forward I hope to be able to get a real unique id for LayerCollections. Given that this is a fundamental change, I'm not even sure if it should be added to 2.83 when it's (hopefully) going to change for 2.90.
(Unfortunately this will mean that after switching over to proper unique ids (not the test fix) the addon will be entirely incompatible with any versions prior to 2.90)
Fri, Jun 5
Jun 2 2020
I like it. I think it looks very good, but I don't know much about the fine details of typography. Interestingly enough, something like your "example tooltip" has been proposed in the past. And I think many people would appreciate the ability to use bold or italics in tooltips (or anywhere) to differentiate sections. I hope this works out!
Jun 1 2020
@Campbell Barton (campbellbarton) Thanks for fixing this. Everything works perfectly now! :D
May 30 2020
Could a unique id be added to LayerCollections and exposed to the python api?
How about mentioning it here?
Yeah, that's probably a good idea. Will do.
May 29 2020
@Dalai Felinto (dfelinto) Sorry, my last post wasn't clear. There's an easier way to recover from this than saving and re-opening the blend file, just click the data icon that's beside the object in the outliner (the green triangle in the default blender theme). This takes you to edit mode and then you can switch back to object mode and everything will be fine.
I guess they were only focusing on managing collections with the Outliner.
Currently, I'm thinking I might be able to make this work by getting the memory address of the collection with as_pointer() and using that as an id.
May 28 2020
Well, we can use an active for bookmarking collection, I guess)
I know, I wish it could have been possible to use the selected row as a bookmark, but the jumping around was just untenable and changing the selection was the only way I could find to solve it. But using the active collection as a bookmark is a good idea.
May 27 2020
Actually I just found a couple of ways to recover from this. You can reset the active object using the python console, save and reopen the blend file, or (the easiest way) you can just click the green mesh data icon for the object in the outliner which sends you to the object's edit mode and from there everything works again.
May 26 2020
- Fixed a problem where the list index could become invalid preventing you from adding collections if no collection was selected in the Collection Manager.
- Fixed the tree view jumping to the selected row whenever you expanded or collapsed a sublevel by selecting the row when expanding/collapsing it. *Sorry to anyone hoping to use the selected row as a bookmark, but you can't work with even semi-long lists with the view jumping all over the place.*
- Fixed an error when switching to QCD slots where there are objects in either pose or weight paint mode and added missing hotkeys to these modes.
Since no one had any objections to my proposed fix and @Paul Kotelevets (1D_Inc) approved of it, I have committed it to blender 2.83.
Any update on this? I'm really trying not to be pushy and I'm sure you have lots of things to deal with, but I'd prefer it if my addon wasn't released with blender 2.83 (LTS) with a bug where loading factory settings completely breaks it.
@Paul Kotelevets (1D_Inc) Thanks, this helps.
This seems like a serious issue, so I'm tagging with 2.83. I hope this is alright.
This seems like a somewhat serious issue, so I'm tagging with 2.83. I hope this is alright.
May 25 2020
I just found a bug with QCD and armatures that are in Pose Mode. If you try and switch to a collection that has an armature in Pose Mode you get a python error. Now this can be solved in a couple ways, but since I don't do that much animation I thought I'd get peoples opinions. Here are the options:
May 24 2020
May 23 2020
May 20 2020
I would want support for this. My addon centers around the use of a UIList and there are certain cases where improved handling of row height would be very beneficial. If nothing else, it would be nice to be able to set the row height without it changing the window size and messing up the scrolling (supporting multiple row heights in the same list would be great too, but I have no idea how hard this would be).
May 18 2020
I think you've found a bug there. When I try working with the Subdivision Set operator in a global context all kinds of weird things happen. In fact the Subdivision Set operator seems to display unexpected behavior (to the user at least) even with the default keymap.
@Jesse Y (deadpin)
You can already do that. Just add a keymap entry to the 3D View (Global) section (or the Window section which is truly global). This will make it work in any mode, so long as a keymap entry in a specific mode doesn't override it. I think the reason why people add multiple keymap entries is because they want it to be there for only some modes, not every mode.
May 17 2020
May 15 2020
General Zip Update:
May 13 2020
I like this in general, but I'd also like to request that an "Advanced Mode" be retained which would show the version we have now, because of things like what @Andrei Nadin (AnadinX) said about having a list that spans multiple contexts, and for the ability to have multiple keymaps open at the same time which it looks like the new design wouldn't allow. But for general use and conflict detection this looks like a great improvement!
May 12 2020
T76635 may be one to include here.
How about turning "breadth first" into a link to the wikipedia page on this subject? It provides a detailed explanation and several images showing the process.
May 11 2020
May 8 2020
May 7 2020
Thanks @Sybren A. Stüvel (sybren) !
- Fixed a couple non-RTO operators not being disabled in Phantom Mode.
- Fixed the Exclude operator resetting the active collection to the Scene Collection unnecessarily.
- Fixed Add Collection and Add SubCollection having the same tooltip.
May 4 2020
This happens in 2.83 as well.
May 3 2020
I probably should have done this to begin with, but with the changes in T74157 I guess I'd better add a menu entry for the Collection Manager, and maybe for other things, for 2.90.
We are using Shift+' combination for toggling between all slots and actual slots combination, I was about to propose it to edit mode slots keys.
What about Shift+= ? It's on the same row as the rest and it represents the plus key which seems like a good way to remember it.
May 2 2020
May 1 2020
Operator alignment test:
@Julian Eisel (Severin) How do you add a disabled hint to a tooltip in python? I'd like to add some to my addon, but can't find any references as to how to accomplish this.
Apr 30 2020
Apr 29 2020
Object selection test based on suggestions from the blenderartists thread post 108 and on.
(See the post for details and hotkeys)