Like, would like more if…

I have tried both local hard disk and online only options for the folders that contain images in the document, and in each case chosen to unlink and relink app to dropbox. They all remain still as "Linked remote" and cannot demonstrate their location on dropbox in anyway. Will not show in finder. Will not open to edit either within personas or other applications - despite paths being clearly and correctly shown at base of Resource Manager window. Tried saving the Publisher file to local desktop too to see if that rewrote the ties… No it didn't.

For the purpose of keeping local hard disks flexible and not overloaded all files are stored online. This hasn't been an issue to date (since the Link Services introduction) but has become so and not sure when/why. I will attempt localising perhaps the latest created publisher on work files - but the images and other artwork resource libraries are too big to have both online and offline - but the fact that "Collect…" locates files with no issue suggests there is something wrong with "Show in finder" and ability to double click and edit Linked (remote) files. Interestingly the large photo resource library i referred to is set to be available locally as well as on line and some of the used folders for artwork items also. The day to day work files offload online via Dropbox's auto offload sync process.

Late to this party but suffering with the same Linked vs Linked (remote) issues which make opening and editing linked files impossible. My partners and I share Dropbox as a working environment using Mac Studios M1 Max chip. We are currently on Sonoma 14.6.1 and Affinity Suite 2.5.3 The Linked Services setting has been working well, however now anything placed by my partners on their macs becomes Linked (remote) on mine, and while displaying the same root path ../CloudStorage/Dropbox/Work/etc… nothing will open as a link to be edited, nor will it "Show in finder". Show in finder just highlights iCloud Drive in sidebar (not relevant and not a used storage location) despite the paths showing identically as highlighted before in the Resource Manager panel. Is this a new issue or is there a fix I can implement? Painful on large files using multiple source locations to pull them all together. (This issue is possibly linked also to the offering of a "Recovery file" after I edit and save a file originally saved by someone else). I have unlinked and relinked Dropbox to see if there was an issue there… no change. As it can't "Show in finder" I thought I'd test that with "Collect…" and it clearly knows exactly where the files are and drops them all into a folder of my choosing, reclassifying as "Linked" having fetched them from various locations – go figure!

Excellent thanks Walt, great explanation of the font dilemma/behaviour and the \K command was the exact code behaviour I had tried to replicate with various look ahead and behind options from the many Regex directories I had found on line to isolate the number before applying style. None featured \K. Not having a crib sheet for regex affinity style or being overly familiar with it in general I had made some but not enough progress. I know many of the examples I had found needed to use regex in the replace too which is not an option. Do you have a reference to the format of regex used in Publisher? It would definitely be a useful crib sheet for the next query.

i have been recently trying to find a way in Publisher to format measurements throughout a document with ease. As stylesheets cannot contain GREP functions as InDesign does to recognise cm3, m2, mm2, in2 etc patterns in the text and fomat as you go. I thought after spending some time looking at Regex tutorials and discovering a formatting function under Typography > Figures that I was onto something. Using regular expressions I can locate any word string that ended with a measurement format and a figure as above and apply Typography > Figures > Superscript to the found characters. Looked good in tests until I add in2 as an option. So it works by finding cm, mm or km etc followed by a numerical character positioned at the end of a word. Find regex: (m|mm|cm|km|yds|in)(\d\b) And then replace with a character stylesheet which makes no change to the underlying text except to convert all figures to superscript. There then appears to be some issues with identifying "figures" within fonts, and not consistently either. See PDF attached. I've used multiple font examples to demonstrate two things, select "Superscript" from the character panel and the entire font can be successfully superscripted. Select superscript on the panel under "Typography" and outcome is bizarre and echoed when using same technique in a character stylesheet. I'm guessing the error is in the code that identifies character types within the font. Over to you. And any better suggestions for identifying just the number in regex search so that I could apply superscript under "position and transform" (can't figure out positive look behind for mm, cm etc) would be gratefully received! Superscript example.pdf

Thanks for that, hadn't seen the update states explainer - and while it might seem to make sense to some, I agree with your original observation, otherwise historical states (which I'm using to build and unbuild a diagram for export) get rendered useless if you need that new content added at various points.

Using this for the first time this may be user error or misunderstanding, however I created and then broke down an illustration with a number of Groups and layers named for finding under Queries. These worked great. I then used these switched options to create captured states. I then needed to add another switchable option, created new content as both a Layer and a Group. Both will switch through Queries panel, but the new artwork will only turn on in my new "final" state (OUTPUTS) and unlike other captured states will not switch off when selected. So I assumed – Select the state you already have but want to remove new content from, switch off new query, update state. However if I click the final state, new layer switches on, but none of the updated states will switch it off. If I manually switch the query off it will then not appear again until I select my final state. I notice that the number of layers has not increased in the original states to match the number in the final added artwork - is this the issue? Shouldn't an update to a state capture all the content of the document? To get to the desired result again I had to recapture all 10 states – not great. But all states then contain same number of layers. ––––––––––––––––––––– AND… Is there a reason why you can't rename a query or captured state?

This seems to be a "specific file" issue. I have created a couple of new files similarly to Hangman and it's all good. Checked with my work partner on identical equipment and he said his is behaving as it should. So seems I have a "problem" file. Will try and resolve that issue tomorrow. Not a bug… just a glitch I hope. This is not a bug but as hoped above a glitch in the file, don't know where or why, but updates to both Affinity and OS have occurred since original file creation in February. Fixed by creating new file, importing colour palette from old doc - important as global colours - then cutting and pasting content into new file. Happily back on track.

@Hangman exactly that, yes.

Yep that's a beautiful demonstration of exactly what's no longer happening here and the process I have enjoyed. The M1 chip seems to feature in a lot of serious performance issues (particular PDF export and transparency issues), but this export was fine in previous versions and has been in regular use for years… so Sonoma (maybe)? Have tested on latest Beta 2.4.0 (2301) and the same result.

Is this a bug introduced in 2.4.0? I have regularly used the auto continuous output of slices and artboards via export persona in the past to allow collaborators to see where a job is at, or instantly update email components for use elsewhere for example. I cannot however manage to get this to work at all today. Export slice - yes. Continuously - no. I have tried app and mac restart, recreated wanted slices (as duplicated file so sometimes they fail), checked, unchecked and rechecked "continuous" and cannot think of anything else to make function. Is this just me? Frustrated at having to manually export via Export or revisit Export persona to select and export.

Yep Affinity 2.4.0 on Sonoma 14.2.1 Up to date to everything and nothing has changed.

This is still a major issue on my M1 mac. Hadn't really noticed until working on a more complex illustration where I have chosen to use 3d on lines with shadows, and colour and gradient overlays to make repurposing objects easy by just changing under laying colour. Having just tried to render a PDF I discover that none of this renders at all… or if it does its transparency fails throughout. Shadows end up as grey brush strokes criss crossing with no transparency, all subtlety lost. Colour & gradient overlays disappear. Why has this not been fixed… everyone here relies on PDFs to share and print files. THIS IS A MAJOR ISSUE.

Thanks, I did go searching and my chosen words revealed nothing so I thought I'd put it out there… just in case! At least there is a work around - just a frustration to require it. Sorry to double/triple up. Also affects expanding stroke - creating holes in the overlap. No need for any further comments, just nice for it to be addressed at some point.

Strange transparency rendering behaviour when adding transparency to individual lines created with arrowheads. This has probably been a forever thing, but have just bumped into it again when fading parts of a flow build. If you create a single line with an arrowhead (curve layer) and change the layer transparency, designer renders the line and arrowhead as individual objects, which given that they are overlayed to prevent gapping creates a more dense area where the line meets the arrowhead. Work around is to group the object… which seems like an odd thing to need to do for a curve line that should behave as a single object. I can't think of an application where I would want/expect the current standard behaviour.