Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Scope of graphic features #489

Copy link
Copy link
Closed
@kushalkolar

Description

@kushalkolar
Issue body actions

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.