| Summary: | Not reading EMF+ EmfPlusPath records correctly | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Chris Sherlock <chris.sherlock79> |
| Component: | graphics stack | Assignee: | Chris Sherlock <chris.sherlock79> |
| Status: | RESOLVED INSUFFICIENTDATA | ||
| Severity: | normal | CC: | chris.sherlock79, gang65, xiscofauli |
| Priority: | medium | Keywords: | filter:emf |
| Version: | Inherited From OOo | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 55058, 103859, 129138 | ||
| Attachments: | EMF+ Joint line | ||
|
Description
Chris Sherlock
2019-12-10 11:55:57 UTC
Hello Chris. Do you have example EMF+ image which demonstrate using of such PathPointTypes? It will be really hard to verify if it is working correctly without some reference image. I will try to create such image. Created attachment 156763 [details]
EMF+ Joint line
It seems that joints are not rendered correctly,
code:
GraphicsPath path;
Pen penJoin(Color(255, 0, 0, 255), 8);
path.StartFigure();
path.AddLine(Point(50, 200), Point(100, 200));
path.AddLine(Point(100, 200), Point(100, 250));
penJoin.SetLineJoin(LineJoinBevel);
graphics.DrawPath(&penJoin, &path);
Bartosz, that's a different issue I'm afraid. We don't seem to correctly support bevelled lines correctly, but that's a different issue to EmfPlusPath objects. Might be worthwhile logging a new bug about mitering (we currently don't support SETMITERLIMIT). [Automated Action] NeedInfo-To-Unconfirmed Hello Chris, Could you please attach a screenshot showing how the file should look like ? Dear Chris Sherlock, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping Dear Chris Sherlock, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp |