Refactor Transition effects #11

Open
opened 2025-07-19 23:29:24 +02:00 by rowan · 0 comments
Owner

Rename FadeEffect to OpacityTransition or FloatTransition and separate the coupling from AddTransition.

Reasoning
This will better position the system to handle arbitrary transition effects whether they're pre-configured in the UXML or not. AddTransition can be responsible for adding the transition if it doesn't already exist (which does not necessitate that the effect will be triggered by the effect system -- it could be a cursor hover effect, for example)

Rename FadeEffect to OpacityTransition or FloatTransition and separate the coupling from AddTransition. Reasoning This will better position the system to handle arbitrary transition effects whether they're pre-configured in the UXML or not. AddTransition can be responsible for adding the transition if it doesn't already exist (which does not necessitate that the effect will be triggered by the effect system -- it could be a cursor hover effect, for example)
rowan added this to the Prototype 1 milestone 2025-07-19 23:29:24 +02:00
rowan added the
enhancement
label 2025-07-19 23:29:24 +02:00
rowan added this to the World Space UI project 2025-07-19 23:29:24 +02:00
rowan removed this from the Prototype 1 milestone 2025-07-20 07:32:16 +02:00
rowan added this to the Prototype 2 milestone 2025-08-01 20:42:24 +02:00
Sign in to join this conversation.
No milestone
No project
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: rowan/canto#11
No description provided.