Bug 497626 - Issues with Numbers Cutting off on Modifier Sliders in Windows11 Style
Summary: Issues with Numbers Cutting off on Modifier Sliders in Windows11 Style
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: 24.08.3
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-12-17 22:30 UTC by Elliot
Modified: 2024-12-22 03:29 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Windows11 Application Style vs Default style (32.87 KB, image/png)
2024-12-17 22:30 UTC, Elliot
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Elliot 2024-12-17 22:30:51 UTC
Created attachment 176722 [details]
Windows11 Application Style vs Default style

SUMMARY: The windows11 Application style is cutting off digits on the slider bars of modifiers.


STEPS TO REPRODUCE
1.  Change the application style in Settings to windows11
2.  Add a modifier such as Crop, Scale, and Tilt.
3.  If the resolution of the video is greater than 2 digits, you cannot see the rest of the digits in the modifier sliders.

OBSERVED RESULT
When using the default style, all four digits show up, but on the windows11 style, the digits are cut off, with no way of extending them.


EXPECTED RESULT
All four digits should be showing up on modifier slider using the Windows11 theme.

SOFTWARE/OS VERSIONS
Windows: Windows 11 Pro
Comment 1 Bernd 2024-12-21 22:44:54 UTC
Can you please update to version 24.12.0 and check whether the issue still exists? The effects GUI has changed quite significantly, and chances are this is no longer a problem regardless of the theme or style applied.

I am putting this report on hold until then. Thanks!
Comment 2 Elliot 2024-12-22 03:29:49 UTC
The newest version does resolve this issue. 

I was only able to download the 24.08.3 version for windows at the time, so I did not know of the issue being resolved.