-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When writing .ocd file all color layers are have the "overprint" flag set #2228
Comments
@FinnAr: I did the following test with Mapper 0.95 and OCAD12:
Thus, I cannot reproduce the issue and also the code to export to .ocd has no pecularities. Can you provide more details or even test files? |
I have the same issue. I can open the map and save it as omap I can also save the map as OCAD but when I import the map into CONDES (10.5.11) I get the error saying that all colour layers have overprint set. I can see the effect in CONDES in the attached example where the road junction in the E doesn't have the black edges suppressed and the dark green overlaps the road to the NE of the building. If I export to OCAD 8 format this does not happen, but any higher OCAD version export (9 to 12) does have the issue. Windows 10 Pro |
I notice in the Condes history of version 10.5.9:
|
Hi MatthiasI did not do any tests with Open Orienteering Mapper myself. My report was entirely based on input from Condes users - and the OCAD files exported from Open Orienteering Mapper they sent me. I apologise for not providing you with sufficient info to reproduce the issue.Thanks to Dave for rectifying this.
|
Hi @FinnAr: I still can't reproduce the issue: The code looks good to me: Could you provide such a map to me (maybe by exporting a small piece?) since the issue should be independent from the number of objects and just depend on the colors. |
Hi Matthias
I think the best bet is to ask Dave for an example – I only have the resulting ocd file exported from Open Orienteering Mapper, not the input file.
|
@DaveIR: I deleted your attachment, as it contains the whole map which was not intended I guess. Always clear the undo history, otherwise the original map can be restored. |
from @DaveIR: Thanks for engaging with this. |
At a first glance: the .omap does not contain any spot colors, thus the Knockout property will always be not set and thus the 'overprint' flag will always be set when exporting to .ocd. |
Hi Matthias
Condes processes the color layers in the same order that OCAD does, i.e. from the bottom to the top Condes does respect the “overprint” flag, and thus applies overprint effect to the color layer on which it is set, which will then “blend” with the underlying layers.
I’m not sure I understand the rationale for not setting the knockout property on all color layers when there are no spot colors. I would have thought that ‘knockout’ would be on as a default.
|
On export don't set the 'overprint' flag for colors without spot colors? |
That would seem to resolve the issue for the case at hand.
From: Matthias Kühlewein ***@***.***>
Sent: 25. august 2024 12:34
To: OpenOrienteering/mapper ***@***.***>
Cc: FinnAr ***@***.***>; Mention ***@***.***>
Subject: Re: [OpenOrienteering/mapper] When writing .ocd file all color layers are have the "overprint" flag set (Issue #2228)
On export don't set the 'overprint' flag for colors without spot colors?
—
Reply to this email directly, view it on GitHub <#2228 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAUCJJTBKFY5XC7U7GEN4ULZTGXIVAVCNFSM6AAAAABGGJQ55KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYG43TCMZVHA> .
You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AAUCJJVMDMFNOHLQBB72RBLZTGXIVA5CNFSM6AAAAABGGJQ55KWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUJTUHB4.gif> Message ID: ***@***.*** ***@***.***> >
|
Steps to reproduce
Actual behaviour
The written file has the "overprint" flag set for all color layers
Expected behaviour
The color layers would be marked with "overprint" if the "KO" flag is not set for that color layer in Mapper, and vice versa
Configuration
Mapper Version: 0.9.5
Operating System: Windows 11
The text was updated successfully, but these errors were encountered: