Created attachment 180194 [details] Properties of Minor Thicks in Ticks tab in Property Explorer *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Default value of the length of minor ticks are very small and "Save Default" doesn't work to change the default value. STEPS TO REPRODUCE 1. Everytime I make a x-y plot, the default value of minot ticks of all axes are very small, and "Save Default" doesn't work to change the default value. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Windows 11 Home 24H2 ADDITIONAL INFORMATION
Git commit e14aca001092d4226733848e12320280abf6fe6d by Alexander Semke. Committed on 17/04/2025 at 17:45. Pushed by asemke into branch 'master'. [worksheet] correctly calculate the lengh of the minor axis ticks when saving the properties as a temlate. FIXED-IN: 2.12 M +1 -0 ChangeLog M +1 -1 src/frontend/dockwidgets/AxisDock.cpp https://invent.kde.org/education/labplot/-/commit/e14aca001092d4226733848e12320280abf6fe6d
(In reply to Yoshinobu Shimamura from comment #0) > Created attachment 180194 [details] > Properties of Minor Thicks in Ticks tab in Property Explorer > > *** > If you're not sure this is actually a bug, instead post about it at > https://discuss.kde.org > > If you're reporting a crash, attach a backtrace with debug symbols; see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports > > Please remove this comment after reading and before submitting - thanks! > *** > > SUMMARY > Default value of the length of minor ticks are very small and "Save Default" > doesn't work to change the default value. The default value for the length of the minor ticks is 3pt. Saving a custom value as a template was wrong for this property which we fixed now. Thank you for reporting this issue. If this feature is critical for you, please consider using our development version until we released 2.12.
Thank you for your reply and quick response to correct the bug. Thanks!