Bug 464131

Summary:	LaTeX label for XY-Plot is wrongly scaled if rotated
Product:	[Applications] LabPlot2	Reporter:	shops
Component:	frontend	Assignee:	Alexander Semke <alexander.semke>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	2.9.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description shops 2023-01-11 07:41:01 UTC

LaTeX label for e.g. XY-Plot is wrongly scaled if rotated. In fact, you can not read LaTeX Plot labels.

STEPS TO REPRODUCE
1. Create a new XY-Plot from some data
2. Edit the Axis-Titel for the Y-Axes to contain LaTeX-Code and styling
3. Make sure, the text is 90° rotated

RESULT
Wrong scaling and rotation of the Label


EXPECTED RESULT
The Label should be correctly displayed, like in the normal "Text" case.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Alexander Semke 2023-01-12 07:22:51 UTC

(In reply to shops from comment #0)
> LaTeX label for e.g. XY-Plot is wrongly scaled if rotated. In fact, you can
> not read LaTeX Plot labels.
> 
> STEPS TO REPRODUCE
> 1. Create a new XY-Plot from some data
> 2. Edit the Axis-Titel for the Y-Axes to contain LaTeX-Code and styling
> 3. Make sure, the text is 90° rotated
> 
> RESULT
> Wrong scaling and rotation of the Label
> 
This was reported  a couple of month ago already in https://bugs.kde.org/show_bug.cgi?id=462671 and we fixed this issue. The fix will be included in the next release 2.10. If you need this fix sooner and more urgent, please use our current development version ("nightly build") which is very close to what is going to be 2.10 soon.

*** This bug has been marked as a duplicate of bug 462671 ***

Comment 2 shops 2023-01-12 07:25:24 UTC

> This was reported  a couple of month ago already in
> https://bugs.kde.org/show_bug.cgi?id=462671 and we fixed this issue. 

Oh, sorry, haven't found that report, sorry! Thanks for fixing and hinting to 2.10. :-)