mirror of
https://github.com/NickeManarin/ScreenToGif.git
synced 2026-04-25 15:15:51 +03:00
[GH-ISSUE #474] StartUp Window #394
Labels
No labels
copy cats
duplicated
future feature
pull-request
⬜ Accepted
⬜ Completed
⬜ Help Wanted 💪
⬜ In Progress
⬜ Missing Details
⬜ Pending
⬜ Waiting For Answer ⏳
🆕 feature preview
🔷 Bug 🐛
🔷 Out Of Scope
🔷 Out Of Scope
🔷 Question
🔷Enhancement
🔷Enhancement
🔷Invalid / External
🔷Knowledge Base
🔷Won't Fix
🕑 High
🕑 High
🕑 High
🕕 Medium
🕙 Low
🕛 Critical
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ScreenToGif#394
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @smaragdus on GitHub (Apr 10, 2019).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/474
In version 2.17 'Options' box in 'StartUp Window' remains highlighted after 'ScreenToGif - Options' window has been closed, screen:
While in version 2.16 the highlighting is automatically cleared after 'ScreenToGif - Options' window is closed, screen:
Is this a bug or a feature? I prefer the behaviour of ScreenToGif version 2.16.
@NickeManarin commented on GitHub (Apr 10, 2019):
It's a feature... Now you now that the keyboard focus is set to that button. If you press Enter you know that it will open the Options.
The same happens with other buttons, even with v2.16. I just applied the same logic to all buttons.
Of course, if annoys more than helps, I'll have to thinker with the styles again.
@smaragdus commented on GitHub (Apr 10, 2019):
@NickeManarin
This is a minute issue if I can call it an issue at all but it somehow irritates my eyes.
I opened this "issue" because I didn't see any information about this change in the change log.
Off-topic
When are logs supposed to be saved- only after there is a problem? I cleared all old data and I didn't find any new logs saved.
@NickeManarin commented on GitHub (Nov 4, 2019):
I forgot to answer this... Well, only if I set to save a log. Usually when it crashes and the code that detects the crash can run normally. Some crashes will close the app even before the log can be saved.