RNA: generate valid infinite float property default values #113854
No reviewers
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#113854
Loading…
Reference in New Issue
No description provided.
Delete Branch "dr.sybren/blender:pr/rna-float-infinite-defaults"
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?
In
makesrna
, generate valid default values for float properties, when those defaults are positive/negative infinity.Blender would currently generate the strings
inff
and-inff
, which are not valid C++. This PR changes that tostd::numeric_limits<float>::infinity()
and-std::numeric_limits<float>::infinity()
.Context: the layered animation system (see #113594) will have animation layers with strips on them. It will have the concept of "infinite strips", where from a user's perspective there aren't even any strips at all, and the layer seems to directly contain the keys themselves. This is purely a UI distinction though, where we simply won't draw the outline of infinite strips. Being able to work with ±∞ as floating point values has clear advantages, as then the
strip.frame_start
andstrip.frame_end
properties will always "tell the truth".This particular change is necessary to allow these values as defaults. It is not intended that users will have property sliders for these properties when their value is "infinite" (but rather a button 'make finite' or something along those lines), so interaction with the UI code will likely be minimal.
That looks good in general, since current behavior is broken anyway. But have you also checked how the python binding code deals with these new float values?
Yes, it works just fine. I can assign
strip.frame_start = -inf
just fine.Even the sliders display the values pretty well:
Editing doesn't work properly (the hard limits are still
FLT_MAX
), but that's not for this PR. I just wanted to be sure that nothing would crash when displaying those values, and that's all 👌 .LGTM then, thx.