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
Right now graphic features mostly map to pygfx buffers, except for present, deleted and thickness (for lines). I'm wondering what attributes we should and shouldn't make as "graphic features". For example, the current primitive legends take a label: str kwarg. If Graphic.name is a feature, the legend labels could automatically track any changes in the graphic name. But should other things like rotation and position also be a feature? Or should the users just use groups or make their own systems for keeping track of changes to things like name, rotation, position.
Make sliceable features return instances, but non-sliceable properties (ex. Graphic.name) just return the corresponding underlying data, ex: Graphic.name returns a str NOT a GraphicFeature instance.
Activity
kushalkolar commentedon May 15, 2024
Make sliceable features return instances, but non-sliceable properties (ex.
Graphic.name) just return the corresponding underlying data, ex:Graphic.namereturns astrNOT aGraphicFeatureinstance.