Pauls

I've raised an issue and I'll bump another regarding the default value in case someone is setting it to zero to create a solid line. I'm not in a position to provide timelines I'm afraid. If you come across similar problems it is possible to go through documents and use The Select, Object, Dashed line menu option to track them down

do you have more than one affinity app open at the same time?

do you recall if you set the dashed line style and then set the gap value to zero to effectively turn it into what looks like a solid line or if they were copy pasted from somewhere ?

@agray for the Education Signage file has similar dashed lines on Page 2. The delimiters used for the Ballroom dimensions. Also the protected backround shape used on all pages is a text shape which appears to also be causing a problem - consider changing that back to a regular rectangle

@atardvark I suspect this may be due to a quirk of the 'Fredrika the Great' font but I'll have to pass this on to the developers for further investigation. Workarounds would be to rasterise any layers using that font or choose another font

There are also a lot of these on the final page - once corrected the file will export in a speedy fashion

@agray - apologies for the delay - I'm looking into your fies and have discovered there are some places where objects have a dashed line style which is causing the slow down. e.g the Sponsor Pavillion Tower file has a group on the first page containing the "Monday October 2" text . This group has rectangles which have the following line style defined on them switching these to solid lines will resolve the issues. They may of course be many other instances. I'm not sure what the cause of these are - it may be some upgrade issue if the files are old or maybe an accidental click. I'll continue checking this file - Just wanted to let you know We're looking into the issue

@MentalFlight are there any invalid or problematic profiles listed in the ColorSync utility ?

what language is the text set to ? maybe the relevant text has not been defined via the Cross references panel

Numbered Paragraph will include the paragraph text upto whatever the sub field limit is ( . is a terminator by default). I've l;ogged an issue to see if we can exclude terminating charcters in the numbering section for this field

I can get something similar by switching documents, going to a different page and trying to activate a different text frame on that page. Focus seems to stay on a previously selected text frame. Update - the new text frame was linked so focus was staying at the story end which was on the previous page.

what settings are you using to create the cross references ?

@HangmanI've recreated that font size issue from PDF and will log it

Anchor name will supply the name of the index mark too

https://www.windowscentral.com/how-use-event-viewer-windows-10

the event viewer log for applications may contain some usefull informatino regarding the crash as well. If you can find an error entry that would be usefull to screenshot

The selection is actually a pixel selection which is why the units are forced to pixels. Displaying document units was a bug in the earlier version. As @NotMyFault says a feature request would be the way to go

oddly it is possible to place the image then edit that placed image - not sure if they are any sublte differences though

Yes the have the html file I find it best to download the whole folder from github then copy the dictionaries you want from there

Typically this is because you have downloaded the wrong thing. It is quite common to get the html page the language pack is on rather than the pack itself. If you post that here we can check if that's the case. You can also download some we saved earlier here

Thanks @MikeTO logging those now - I dont think the anchor panel has a context menu also if there is only one action I would expect it to be a double click.

does disabling the effect check box and then re enabling it restore normal operation ?

thanks for the report - we've recreated this internally it seems to be related to the iPad model(s) we think

I see the issue with point 8 now and have logged an issue for that

@SenecaI can see why you would like to specify a range for a cross reference but i feel that would be too much work to fit into this cycle. It would be a USP for this feature