Skip to content

Scope of graphic features #489

Closed
@kushalkolar

Description

@kushalkolar

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

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy