The bl_width_max property of nodes reset to 320 automatically #46345
Labels
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#46345
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Windows 7 64 bit
Blender Version
Broken:
e511710
Short description of error
For some nodes it can be useful when they are wider than the normal max value of 320.
To make them wider I first increase the bl_width_max value of the node and then I change the real width.
This works all fine but sometimes the bl_width_max property resets back to 320 after saving, closing blender, and reopening the file again.
Why is there a max value anyway?
Changed status to: 'Open'
Added subscriber: @JacquesLucke
Added subscribers: @JulianEisel, @mont29
Please always include a .blend file and precise simple steps to reproduce reported issue…
@JulianEisel maybe you know about this and/or are interested to investigate too?
Ah sorry. Here the file. Just open it and try to make the node larger or smaller.
bl_width_max_bug.blend
Thanks, yes, something seems odd here… might be versionning too?
Added subscriber: @brecht
It shouldn't be possible to modify
bl_width_max
, that's a property of the node type not the node and should only be set when a node type is registered.I'm not sure why node types have these fairly limited max values, probably they could be increased.
Agree with @brecht. I'm not that familiar with RNA internals, but think we can just do this to disable tweaking for register values:
We can also easily increase max size for nodes, just depends on what value is appropriate. What about say 640?
Also, I think minwidth & maxwitdh should be scaled with U.pixelsize (at least maxwidth).
Added subscriber: @ideasman42
If that works and doesn't break registration that seems ok. Though would be good to check with @ideasman42 if there could be scripts depending on these being editable.
Regarding pixel size, I'm not sure why it should be scaled, I would expect the node editor to do that kind of conversion in the drawing code. There should be no detectable difference in the Python API as far as I know.
Increasing the 320 to some higher number would be ok for me but I wonder for what this property is needed and why it has to be such a 'low' value. Happens something bad when the width is 10.000 or so? Not that I need such a wide node, but why is there this limitation?
This issue was referenced by
867c49b962
Changed status from 'Open' to: 'Resolved'
LGTM, @JulianEisel, committed as you :)
Thanks :)
@JacquesLucke, I see your point, question is if such huge values are any more useful. I don't think so, I'd say a default maxvalue of 640-1000 is okay.
Yes okay. I just found a work around for me.
All nodes in my Addon are subclasses of bpy.types.Node and AnimationNode. When I make bl_width_max = 5000 as class property of the AnimationNode class then all other nodes uses that max value.
But yes. I guess 1000 is definitly enouph.
Thanks! :)