Display points #27

Open
opened 2024-12-04 20:10:07 +00:00 by Vectornaut · 2 comments
Collaborator

Show points in the Display view.

Styling

  1. Emphasize that a point has no part. For example:
    • No partial occlusion, even when the point representation (presumably disk or sphere) is only partially shaded by a surface
  2. A point that lies on a positive-codimension entity is never occluded by its neighborhood in that entity (but might be occluded by some region of that entity not containing it, such as a point on the "back" hemisphere of a sphere being occluded by its "front" hemisphere).
  3. Maybe a point that's constrained to be on a surface should be flattened onto the surface? (Likely this would be a later experimental refinement of the visual representation.)

Labeling

  1. Label always has the same apparent occlusion as the point.
    • In particular, when a point lies on a positive-codimension entity, its label is never occluded by its neighborhood in that entity. This is a corollary of (4) and (2).
  2. Label stays in the same screen orientation and position, relative to the point, under most or all rotations.
    • Labels are always "upright" for reading in the display, unless explicitly customized on a per-point basis or generically. (Such angled label text can be a later enhancement.)
    • Maybe it would be okay for the label's screen orientation to roll when the camera rolls (respecting previous bullet).
    • Ultimately the apparent relationship of label to point should be customizable (e.g. by dragging the label, but perhaps in other ways, such as a selection of placement algorithms) on a per-point basis, falling back to a (potentially customizable) general default.
Show points in the `Display` view. ### Styling 1. Emphasize that a point has no part. For example: - No partial occlusion, even when the point representation (presumably disk or sphere) is only partially shaded by a surface 2. A point that lies on a positive-codimension entity is never occluded by its neighborhood in that entity (but might be occluded by some region of that entity not containing it, such as a point on the "back" hemisphere of a sphere being occluded by its "front" hemisphere). 3. Maybe a point that's constrained to be on a surface should be flattened onto the surface? (Likely this would be a later experimental refinement of the visual representation.) ### Labeling 4. Label always has the same apparent occlusion as the point. - In particular, when a point lies on a positive-codimension entity, its label is never occluded by its neighborhood in that entity. This is a corollary of (4) and (2). 5. Label stays in the same screen orientation and position, relative to the point, under most or all rotations. - Labels are always "upright" for reading in the display, unless explicitly customized on a per-point basis or generically. (Such angled label text can be a later enhancement.) - Maybe it would be okay for the label's screen orientation to roll when the camera rolls (respecting previous bullet). - Ultimately the apparent relationship of label to point should be customizable (e.g. by dragging the label, but perhaps in other ways, such as a selection of placement algorithms) on a per-point basis, falling back to a (potentially customizable) general default.
Vectornaut added reference main 2024-12-04 20:10:21 +00:00
Vectornaut removed reference main 2024-12-04 20:10:24 +00:00
Vectornaut added the
enhancement
label 2024-12-04 20:10:42 +00:00
Owner

Note that a first PR would presumably only implement the core of the features listed above; its merge should be accompanied by filing issues with the remaining desired features and resolving this overall one.

Note that a first PR would presumably only implement the core of the features listed above; its merge should be accompanied by filing issues with the remaining desired features and resolving this overall one.
Owner

Are points already fully supported in the Assembly and Engine? If not, it would seem that issues for such support should be filed now, and at least the Assembly one should be a prerequisite of this one.

Are points already fully supported in the Assembly and Engine? If not, it would seem that issues for such support should be filed now, and at least the Assembly one should be a prerequisite of this one.
Vectornaut added this to the Demo project 2025-02-11 00:25:16 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: glen/dyna3#27
No description provided.