[GH-ISSUE #442] [Feature Request] UI: Grouping / classing overlay elements (low priority) #364

Open
opened 2026-02-26 09:31:10 +03:00 by kerem · 1 comment
Owner

Originally created by @vatterspun on GitHub (Jan 28, 2019).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/442

I had some time today so I started brainstorming possible things that might be useful additions. The process below will probably only save a few clicks so I put the [Low Priority] on the title.

One thing I've noticed is when selecting edits to the file, I always wonder if I need to select all the frames before continuing. As such, I tried to figure out was how to separate the operations that affect the whole animation vs. those that just affect the entire file. I'm not sure if this addresses a real problem or is something users wouldn't just figure out through the course of using the program but maybe it's worth exploring.

Of course the easy thing is just to throw everything under a separate tab:

image

... but this is probably confusing since it duplicates a number of UI elements. And I think the current categories make a lot of sense, especially for new users.

Another possibility is just marking the items a little differently with some kind of legend, either a marker or a different text color:

image

... anyway some ideas.

Originally created by @vatterspun on GitHub (Jan 28, 2019). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/442 I had some time today so I started brainstorming possible things that might be useful additions. The process below will probably only save a few clicks so I put the [Low Priority] on the title. One thing I've noticed is when selecting edits to the file, I always wonder if I need to select all the frames before continuing. As such, I tried to figure out was how to separate the operations that affect the whole animation vs. those that just affect the entire file. I'm not sure if this addresses a real problem or is something users wouldn't just figure out through the course of using the program but maybe it's worth exploring. Of course the easy thing is just to throw everything under a separate tab: ![image](https://user-images.githubusercontent.com/1289134/51808799-3e5c0900-225e-11e9-9bf7-837056525ee3.png) ... but this is probably confusing since it duplicates a number of UI elements. And I think the current categories make a lot of sense, especially for new users. Another possibility is just marking the items a little differently with some kind of legend, either a marker or a different text color: ![image](https://user-images.githubusercontent.com/1289134/51808865-90e9f500-225f-11e9-9c99-90a5b5766302.png) ... anyway some ideas.
Author
Owner

@NickeManarin commented on GitHub (Sep 26, 2019):

I'm planning a redesign for that UI.
I'll reorganize the features based on how they interact with the project.

<!-- gh-comment-id:535638340 --> @NickeManarin commented on GitHub (Sep 26, 2019): I'm planning a redesign for that UI. I'll reorganize the features based on how they interact with the project.
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
starred/ScreenToGif#364
No description provided.