View menu #26

Open
opened 2026-08-09 00:16:27 +00:00 by Roboticy3 · 1 comment
Roboticy3 commented 2026-08-09 00:16:27 +00:00 (Migrated from github.com)

There's been a dummy "view menu" in the code for a while now, just an empty window. I want to be able to control the color and texture of different node types with it.

Currently, all node types are determined automatically. However, I also want to be able to determine types via custom rules set in the view menu, such as "Speaker == "Freya"" or something like that. #11 may be a pre-requisite to doing this properly.

Finally, I want multiple view "profiles" to be bound to Alt+1-9 so the user can quickly switch between multiple views. This behavior can be combined with more advanced concepts like filters and automatic node positioning later.

There's been a dummy "view menu" in the code for a while now, just an empty window. I want to be able to control the color and texture of different node types with it. Currently, all node types are determined automatically. However, I also want to be able to determine types via custom rules set in the view menu, such as "Speaker == "Freya"" or something like that. #11 may be a pre-requisite to doing this properly. Finally, I want multiple view "profiles" to be bound to Alt+1-9 so the user can quickly switch between multiple views. This behavior can be combined with more advanced concepts like filters and automatic node positioning later.
Roboticy3 commented 2026-10-06 18:12:17 +00:00 (Migrated from github.com)

Since I'm working on code completion, it would also be nice to have features like speaker autocompletions coming with the color of that speaker. This could be achieved with a special case for speakers in speaker blocks + speakers in expression blocks that looks up the color against a loaded config, but can't be done right now because the editor doesn't load a speaker config on its own. That's probably a prerequisite for this issue and for debugging with the editor and the new engine in the future.

Since I'm working on code completion, it would also be nice to have features like speaker autocompletions coming with the color of that speaker. This could be achieved with a special case for speakers in speaker blocks + speakers in expression blocks that looks up the color against a loaded config, but can't be done right now because the editor doesn't load a speaker config on its own. That's probably a prerequisite for this issue and for debugging with the editor and the new engine in the future.
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
Roboticy3/Louder#26
No description provided.