You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been looking for a means to easily configure shape definitions such that any user edits (e.g. repositioning the shape) to them are blocked.
At this time of writing, the figure reference for shapes doesn't appear to have a property where one can achieve the above (e.g. an editable property). In case I've missed something in the API that makes this effortless, I'd appreciate any pointers.
In the meanwhile, I guess there are workarounds, such as my following example below which makes use of mouse event handlers:
gvwilson
changed the title
Configuration property per shape to prevent user edits
add configuration property per shape to prevent user edits
Aug 9, 2024
It would be nice to have annotation and shape options to prevent moving / clicking / editing per shape or annotation. I have an example where I want subplot title editable but not movable. System chart shapes that should not move or resize and user shapes that should just move or both.
It would be nice to have annotation and shape options to prevent moving / clicking / editing per shape or annotation. I have an example where I want subplot title editable but not movable. System chart shapes that should not move or resize and user shapes that should just move or both.
This is similar to what I want as well. Instead of all-or-nothing editable:true/false, I'd like to be able to set editable:false, and then override it for individual shapes.
Hello,
I've been looking for a means to easily configure shape definitions such that any user edits (e.g. repositioning the shape) to them are blocked.
At this time of writing, the figure reference for shapes doesn't appear to have a property where one can achieve the above (e.g. an
editable
property). In case I've missed something in the API that makes this effortless, I'd appreciate any pointers.In the meanwhile, I guess there are workarounds, such as my following example below which makes use of mouse event handlers:
Here's a CodeSandbox setup with the above.
The text was updated successfully, but these errors were encountered: