[Feature Request] Option to set color of Recorder window separate from rest of Color Scheme #538
Labels
🔷Enhancement
Type • Improvements for the software.
future feature
The developer wants to implement this feature, but it's uncertain when it will be available for use.
Currently, setting a color scheme affects all windows (including the Options dialog).
However, there seems to be two kinds of window in ScreenToGif: ones which use native title bats and ones which don't. The windows that use native titlebars are fine and easy to see (as this uses the Operating System's theme as specified by the user). But for certain other windows (e.g. Recorder and Board) the window border theme has been hard-coded and over-rides the default OS window styling.
Choosing a light option that looks good in native windows results in a super-pale white scheme in the non-native Recorder and Board windows. This makes it almost impossible to see against any typical page (which usually a white background) resulting in a white on white situation.
However, changing the color to improve visibility also changes the background of the Options page, making the text harder to read (unless you switch to dark, or very dark).
Therefore it would be helpful to have a separate color option that affects recording screens and another one for the rest of the UI (e.g. options).
Alternatively (I don't know if this is possible) perhaps use native OS window borders for all ScreenToGif windows (including the Recorder and Board windows). This means that it will always blend with whatever Operating system it is being run on. This is particularly noticeable on Windows 7 (where the non-native titlebar border theming of the Recorder and Board windows is really noticeable and jarring).
The Webcam recorder and Editor windows already use native OS window theming, so perhaps this could be extended to the other windows too (which would negate the need for separate color scheme options for different parts of the program because window borders would all be consistent and easily visible).
The text was updated successfully, but these errors were encountered: