StudioInfinity/dyna3
2
0
Fork 2
Code Issues 65 Pull requests 2 Projects 3 Releases 4 Wiki Activity Actions

Hide and show elements in the graphical view #71

New issue
Open
opened 2025-03-10 23:47:56 +00:00 by glen · 1 comment
glen commented 2025-03-10 23:47:56 +00:00
Owner
Copy link

Not necessary for the tech demo, but seems like definitely an alpha-level feature, because the graphical view can get unwieldy and so you sometimes need to temporarily turn off some elements to see what's going on.

Not necessary for the tech demo, but seems like definitely an alpha-level feature, because the graphical view can get unwieldy and so you sometimes need to temporarily turn off some elements to see what's going on.
glen added the
enhancement
 label 2025-03-10 23:47:56 +00:00
glen added this to the Alpha project 2025-03-10 23:47:56 +00:00
Vectornaut changed title from Need to be able to hide/show elements in the graphical view to Hide and show elements in the graphical view 2025-03-11 05:24:32 +00:00
glen commented 2025-10-06 22:57:52 +00:00
Author
Owner
Copy link

Note we now have ghost mode, with an explicit checkbox. There is clearly some overlap with ghost mode. There seem to be two underlying properties here: opacity and graphical selectability. "Hidden" is an opacity of 0 together with selectability false, whereas "ghost" is an opacity of something low together with selectability false. These are both useful, so we might want to have shortcuts for each of these combos. But ultimately we do want to be able to control these underlying properties directly, once we have a more articulated attributes system.

Note we now have ghost mode, with an explicit checkbox. There is clearly some overlap with ghost mode. There seem to be two underlying properties here: opacity and graphical selectability. "Hidden" is an opacity of 0 together with selectability false, whereas "ghost" is an opacity of something low together with selectability false. These are both useful, so we might want to have shortcuts for each of these combos. But ultimately we do want to be able to control these underlying properties directly, once we have a more articulated attributes system.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
readme-toplevel
kaleidocycle-example
outline-update-fix
lang-trials
seed-problem
0.3pre
0.2
v0.1.1
v0.1.0
Labels
Clear labels   
bug

Something is not working

  
design

Issue that entails architecture/design decisions

  
duplicate

This issue or pull request already exists

  
engine

Issue concerning the engine

  
enhancement

New feature

  
maintenance

Refactors andother behavior-orthogonal tasks

  
prospective

This will become an issue once a particular feature is implemented or pull request is merged

  
question

More information is needed

  
regression

A bug that's resurfaced or a feature that's accidentally been removed

  
stub

We need to fill in the details of this issue

  
todo

Planned step in implementation

  
ui

Issue concerning the user interface

  
wontfix

This won't be fixed

No labels
bug
design
duplicate
engine
enhancement
maintenance
prospective
question
regression
stub
todo
ui
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Alpha
Assignees
Clear assignees
No assignees
1 participant
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: StudioInfinity/dyna3#71
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?