Bug 496625

Summary:	Axis title not completely visible
Product:	[Applications] LabPlot2	Reporter:	uwestoehr <uwestoehr>
Component:	frontend	Assignee:	Stefan Gerlach <stefan.gerlach>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version First Reported In:	latest
Target Milestone:	---
Platform:	Other
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	screencast 2 OPJ file used to create the .lml file screencast 1

Description uwestoehr 2024-11-24 00:24:27 UTC

- open the attached .lml file and show the plot
result: the y-axis title is only partly visible, see the attached screenshot

I failed to make it visible because
* changing the main window size does not change anything, see the first screenshot.
* trying to click and drag the title makes the title invisible or does strange things, see second screencast

Note that for the second attempt one cannot undo the actions so one ends up with a messed plot ans is somehow lost to fix its view.

Release build 01487f6
Nov 21 2024, 20:05:46
System: Windows 10 Version 22H2

Comment 1 uwestoehr 2024-11-24 00:25:22 UTC

Created attachment 176069 [details]
screencast 2

Comment 2 uwestoehr 2024-11-24 00:27:59 UTC

Created attachment 176070 [details]
OPJ file used to create the .lml file

Comment 3 uwestoehr 2024-11-24 00:51:29 UTC

Created attachment 176076 [details]
screencast 1

Comment 4 Stefan Gerlach 2024-11-26 21:43:06 UTC

The space available between the axis and the edge can be changed in the plot area settings in the tab "Layout" with "Padding".

Comment 5 Stefan Gerlach 2024-11-26 23:27:16 UTC

Please try the latest build for Windows. The initial padding was improved. Otherwise adjust it in the "Layout" tab of the plot area settings.

Comment 6 uwestoehr 2024-11-28 22:53:15 UTC

(In reply to Stefan Gerlach from comment #5)
> Please try the latest build for Windows. The initial padding was improved.
> Otherwise adjust it in the "Layout" tab of the plot area settings.

Many thanks. I can confirm the bug is there fixed, but I found another one: bug 496803