Layout has changed since file was opened

[arcandio]

Hello folks, I've been loving Affinity Designer so far (aside from the not being able to export a PDF bug occasionally) but I've got a new problem. I worked on a file and exported it to SVG, then when I came back to it several days later, the layout has somehow changed since then, possibly on opening the file. I've attached a before capture of the SVG, and a new capture of the new layout. I haven't changed anything since the last time I edited the file to export the SVGs. I've also noticed that whites are looking pink for some reason now that I open the file again, I don't know if that's a symptom of the same problem (some kind of change to the settings??) or if it's completely unrelated.

It looks like the Text on a Path that makes up the circle somehow had its red and green handles reset, or perhaps the program's algorithm for using the handles has changed, because I'm fairly sure I originally positioned those by dragging both handles to one side so that the entire perimeter was valid text area, then set the text to be centered via a style. Now that I fiddle with it again, it doesn't seem to behave the way I remember, I actually have to slightly overlap the handles to get the entire text to stay on one line.

FYI, I've also tried changing the font size and spacing, to no avail. I don't know whether the app was updated since I last edited the file, but my current version is 1.7.1.404.

I've got a lot of these thingies, so fixing them manually would be a huge nightmare.

Is there a way to fix all the texts on a path at one time?

[Dan C]

Hi arcandio,

Welcome to the forums  

11 hours ago, arcandio said:

then when I came back to it several days later, the layout has somehow changed since then, possibly on opening the file.

When you say this, are you reopening the .afdesign file, or the exported SVG?

11 hours ago, arcandio said:

I've also noticed that whites are looking pink for some reason now that I open the file again, I don't know if that's a symptom of the same problem

This usually happens with a corrupt or incorrect screen colour profile, have you changed any of your colour settings through your OS recently?

Could you please provide a copy of your .afdesign file and SVG to the following link so I can investigate this further for you?

https://www.dropbox.com/request/xiXJC3Mp3PEpSYr98VX8

[arcandio]

When I reopened the .afdesign file. The SVG is correct, and hasn't changed since I opened it, nor has the PNG that I exported at the same time. I've sent the files via dropbox. Thanks for your help!

Regarding the color, not that I'm aware of.

[Dan C]

Thanks for that, it appears that the error is caused by the path end points being coincident . You will notice in your document that when you have the text highlighted, it shows the handles overlapping. This causes an issue with the alignment of the text on the path which should not be happening. This bug is logged with our development team, so I'll bump this thread with your document now.

If you apply the following change to your text, you should find this does not happen again -

Could you please open Preferences>Colour and provide a screenshot of your settings here? Your document appears correctly for me, so the colour issue must be local to your machine.

[arcandio]

Re the handles: good luck to the dev team. I don't really have time to go and manually adjust the handles on all of the tokens at this point, and the issue I was having was that it was tough to adjust them to be perfectly centered the way they ought to be if they were attached to the opposite snap point. Though I guess the remedy to that would be to adjust the handles so they snap to the left and right snap points instead of the opposite side. If I have time to update the file, I'll try that.

Do you suppose that they just happened to be right when I set them up and stayed that way until I saved and closed the file?

Re Color: screenshot attached, with evidence in the background.

 

[Dan C]

I understand, my apologies for any inconveniences caused.

21 hours ago, arcandio said:

Do you suppose that they just happened to be right when I set them up and stayed that way until I saved and closed the file?

Essentially if the path end points are coincident then the file will appear correct, however upon saving and reopening the documents, the points do not physically move but the text updates to be incorrect. If you set up text on a path with coincident points the file will always appear correctly, until reopened. We hope to have this fixed asap.

Thanks for that, do you have any colour profiles set through your OS? What colour format is the document opening in for you?

[arcandio]

I understand. The points aren't moving, they're just being interpreted differently at different times. I'll be aware of that in the future.

Attached the color settings of the document.

I've found that moving AD from my main monitor with a "2351.icm" profile to my second monitor with no icm set "fixes" it, in that file appears color correct. But here's the thing, I haven't opened the color management window up or edited the color settings on my machine for many months, long before I worked on this file. When I created it, it looked correct on that monitor with that profile. I can attach the profile if it helps. Nothing else seems to have this problem on that monitor though.

[Dan C]

Thanks for confirming that and my sincerest apologies for the delayed response.

On 7/24/2019 at 6:09 PM, arcandio said:

I've found that moving AD from my main monitor with a "2351.icm" profile to my second monitor with no icm set "fixes" it, in that file appears color correct

That would indicate that your colour profile may be slightly corrupt, or Affinity is not interpreting it correctly.

On 7/24/2019 at 6:09 PM, arcandio said:

I haven't opened the color management window up or edited the color settings on my machine for many months, long before I worked on this file. When I created it, it looked correct on that monitor with that profile.

Have you updated Affinity between creating and reopening the file? It may have been caused by a change we made in one of our more recent updates.

On 7/24/2019 at 6:09 PM, arcandio said:

I can attach the profile if it helps. Nothing else seems to have this problem on that monitor though.

Please do, a copy of this profile would certainly be useful. This is because Affinity does document to screen colour conversion using the ICC profile - and other apps don't.

[arcandio]

For completely separate reasons, I wiped my machine over the weekend, so I think I lost that 2351.icm file, but I think it was created using the windows tools for color adjustment on a per-monitor basis some time ago.

As for updated between when I created/saved the file and when I opened it again, I don't think so, but if there's an auto-updater, I have no idea. I didn't do it manually to my knowledge.

[Dan C]

Not to worry, thanks for letting me know. I'll have our QA team create a colour profile using this tool and test it in conjunction with Affinity.

There's no auto-updater on Windows currently, so I can pretty safely assume your app wasn't updated between uses.

Thanks for all the information provided, I'll be sure to log this internally so we can investigate this further and improve our colour handling in the future. Many thanks!

[arcandio]

Thanks to you as well for being timely and on the ball. Hope a fix for the original makes it into production at some point.