User Details
- User Since
- Aug 11 2017, 4:33 PM (260 w, 2 d)
Wed, Aug 3
Mon, Aug 1
Mon, Jul 25
Sat, Jul 23
Tue, Jul 19
Just to mention, some users who've downloaded our and used builds have requested to customize these panels even further, either default closed or open, or to show/hide. The user option for these file browser panels should remain.
Mon, Jul 18
Jul 1 2022
Tested, all green from me.
Jun 30 2022
Jun 25 2022
Jun 15 2022
Can confirm, trying to set from Right Click menu on the toolshelf operators goes to wm.
Apr 28 2022
Apr 26 2022
Apr 17 2022
Mar 28 2022
Mar 26 2022
Mar 9 2022
Can confirm the issue, and the fix here.
Mar 3 2022
Feb 14 2022
Feb 9 2022
Jan 12 2022
Dec 20 2021
Dec 14 2021
Dec 7 2021
Looks good. I was needing this the other day, would improve the UX a lot there.
Nov 26 2021
Nov 25 2021
Nov 23 2021
Nov 22 2021
Nov 16 2021
Agree, with a user prop as an option, allow automatically adding the override if the data is linked to a clear and hassle free UX (drag and drop then use - not drag, drop, override, then use)
Nov 15 2021
Nov 9 2021
Removing it is a bandaid solution to the code issues and doesn't address the UX if at all.
Nov 4 2021
Thanks for taking a look at it. When/how will it become a task to get code commit to? Do you track code commits to feature requests somewhere?
Oct 21 2021
Oct 19 2021
This has an issue, now the background colour is decoupled from the theme property of the Node Group colour. This means... group nodes don't have any colour coding - and that prop is now useless. This also clashes with the grid colour, as that doesn't change with the background.
Oct 16 2021
Would this be a part of the "Everything Nodes" development cycles?
Oct 15 2021
I think this is an excellent solution to a community UX debate.
Oct 8 2021
Bump, this needs some polish.
Oct 6 2021
Oct 5 2021
Ping. What is the final verdict for this patch?
Oct 4 2021
Solid line are easier to read and less noise. I would opt to color coding.
Sep 29 2021
Take note, my screen captures are from a custom build of Blender with custom icons.
Sep 20 2021
Sep 16 2021
Aug 23 2021
Aug 22 2021
Wow, the code looks like a small change. Does this apply throughout the entire UI?
Aug 20 2021
Aug 9 2021
Aug 3 2021
Yes, clicking on the right click then sub menu, or going into a sub menu is a little tricky. Making it consistent with the file browser here would make sense.
Jul 23 2021
Suggested expected UX per editor, which can be divided into two levels of UX, the intuitive and the granular:
Jul 22 2021
Can confirm, search doesn't work with Collections. Mesh data yes. Material nodes can be limited.
Is this like an asset reviewer standalone?
This is a pretty big spanner in the UX of joining and merging and applying geometry from instances. If there are no UVs post the modifier - but the instance has one, they should be applied when applied, it is expected behaviour to preserve the legacy UV's without needing to work around.
Jul 14 2021
Jul 5 2021
Jul 1 2021
Jun 29 2021
Proposal B has my vote - even just an unused colour that says "Undefined: will adapt to what you plug in". Not sure about the picker readout proposal of E though, I think the readout should be dynamic to what you plug in.
Jun 28 2021
Jun 24 2021
Jun 18 2021
Bump, will this be implemented for 3.0? I certainly hope so! It looks practically done.