Skip to content

SymbolName limited to vispy marker types #68

@gselzer

Description

@gselzer

As written in #65:

@tlambert03, since you wrote scenex.model.SymbolName: there are many symbol types that pertain only to pygfx that aren't in that list, and conversely some symbols that the pygfx backend can't (without a custom marker type, which is some additional effort) handle.

There are a few ways that we could proceed:

  1. Add pygfx-only types to SymbolName - works, but could drastically expand the size of the Literal, especially if more backends are added. Don't know if this is a problem, though.
  2. Switch to a SymbolName | str, which would keep SymbolName as a common subset but allow each backend to support its own styles as well.

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