Created attachment 57265 [details]
Sample document with screenshots
Arrowhead of Block Arrow shape "Circular Arrow" in document from 3.4.5 looks wrong in 3.5.4 and Master, compare views in attached sample document.
It's not necessary to do all steps as you see in sample, you can simply insert the shape with 3.5.0 and move the yellow control point at the arrowhead.
Was ok until Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: 81607ad-3dca5fd-da627d2)]"
Prolbem starts for me with parallel installation of MinGW Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) English UI [(Build ID: 308b7a2-e916bf9-9c6ea62-e1a2fb3)] (daily/MinGW_cross-compilation 2011-10-18_22.56.49)"
This appears only on those which are scaled differently on x and y.
This has to do something with the circular arcs.
They are always drawn so that the tangents' angles of the arc ends follow the scale warp.
Effect Also to be seen on pacman shape and ordinary arc.
I found out where the bug is.
The multiplier fRatio is totally contraproductive. Why is it there??
No distortion without it.
Patch comes after further testing.
Created attachment 68863 [details]
pdf file showing incorrect shapes
Issue still exists for Version 220.127.116.11+ (Build ID: d401dcc)
OS: Win XP
@ firstname.lastname@example.org I dont get it. I got the latest master, but my code change is still there.
A master two weeks old still works.
May this have to do something with that it was not TAKEN OVER to the windows version repository, or did you compile it from master by yourself????
(Because I removed something in this patch that noone knew what it was for, there was a fear of a regression.)
I cannot compile the current version until I download it new, but I found no newer patch entry that could have done bad things to this. (my change is still the latest in that file, d9f21c90bd61d15fd78a8df9115bf2e9ededbd1b).
(In reply to comment #5)
> May this have to do something with that it was not TAKEN OVER to the windows
> version repository, or did you compile it from master by yourself????
Yes, I believe that is the reason. I tried to reproduce the bug in a version I compiled myself (Version 18.104.22.168.alpha0+ (Build ID: 370m0(Build:0))) and not the one I got from repository and it's working perfectly fine, no distortions. Sorry for causing unnecessary confusion.