Bug 429259

Summary:	Line chart: Option to influence ticks
Product:	[Applications] plasma-systemmonitor	Reporter:	Richard Llom <richard.llom>
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED WORKSFORME
Severity:	wishlist	CC:	ahiemstra, kde, kdedev, plasma-bugs-null
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Richard Llom 2020-11-17 17:20:00 UTC

The ticks in the line chart seem to be hard coded to 4. When measuring a range which is not dividable by 4, e.g. 0 to 90, those ticks are setting at some not so nice marks:
23° 45° 68° 90°

Therefore it would be nice to have some way to influence the tick positions.

Possible solution I came up with:
a)
Set tick grid, eg. 20 for above example would give ticks at 20,40,60 and 80 (the graph would still go to 90). This would be the nicest solution IMHO.

b)
Specify number of ticks, eg 3 for above example would give ticks at 30, 60 ,90. Good solution.

c)
Toggle for even/odd number of ticks. Better than nothing I guess kind of solution ;-)

Comment 1 TraceyC 2025-05-09 19:46:28 UTC

I'm sorry we weren't able to address this before now. The system monitor has had a lot of work since this request was opened. Can you let us know if this is still an issue with Plasma 6.3.5 or later? If so, can you attach a screenshot showing the problem? Thanks!

Comment 2 Bug Janitor Service 2025-05-24 03:47:26 UTC

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Bug Janitor Service 2025-06-08 03:47:40 UTC

🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.