Seneca

Are you in Preview Mode by any chance?

Thanks for the latest beta. Just noticed that the Text Wrap doesn't seem to be working in this beta.

Respectfully, I disagree. Consider this scenario: I want to create a new document with all margins set to 10. I type number 10 in one of the margin fields and only then I realise that I forgot to click on the bind icon to force all fields to the same value. I click on the bind icon and I retype 10 in the same field and tab away but nothing changes. I may not have changed the value of the field but I have changed the meaning of my action by enabling the bind icon.

You'll get all 10s. And you are right unlink is a better term here, I think.

Hi @Old Bruce, it should be difficult. InDesign handles it beautifully. In fact, it remembers the latest input value and it changes all other fields as soon as you enable the lock. In other words, even if you forget to enable the lock, it will still apply that change to other fields as soon as the lock is enabled.

Changing the margins after the lock has been applied using the same input field doesn't update other fields. The only way to change the margins is to do it from another field. See the screencast below. lock.mov

Just a quick note to say that this new version crashes almost instantly every time I open a file created in previous beta version. Process: Affinity Publisher Beta [22640] Path: /Applications/Affinity Publisher Beta.app/Contents/MacOS/Affinity Publisher Beta Identifier: com.seriflabs.affinitypublisher.beta Version: 1.10.0 (1.10.0.1098) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2021-06-24 16:04:05.8680 +0100 OS Version: macOS 12.0 (21A5248p) Report Version: 12 Anonymous UUID: 165FC6DA-6D41-ABF3-EB6E-5B901110B07C Sleep/Wake UUID: 168DB93A-9871-4407-B5EA-10D2463A005D Time Awake Since Boot: 120000 seconds Time Since Wake: 4217 seconds System Integrity Protection: enabled Crashed Thread: 7 Dispatch queue: com.apple.root.default-qos Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x000070000a4beff8 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SIGNAL, Code 10 Bus error: 10 Terminating Process: exc handler [22640] VM Region Info: 0x70000a4beff8 is in 0x70000a4be000-0x70000a4bf000; bytes after start: 4088 bytes before end: 7 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL Stack 70000a43c000-70000a4be000 [ 520K] rw-/rwx SM=SHM thread 6 ---> STACK GUARD 70000a4be000-70000a4bf000 [ 4K] ---/rwx SM=NUL ... for thread 7 Stack 70000a4bf000-70000a541000 [ 520K] rw-/rwx SM=SHM thread 7 Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x7ff807f4473a mach_msg_trap + 10 1 libsystem_kernel.dylib 0x7ff807f44aab mach_msg + 59 2 CoreFoundation 0x7ff8080425d5 __CFRunLoopServiceMachPort + 319 3 CoreFoundation 0x7ff808040c97 __CFRunLoopRun + 1325 4 CoreFoundation 0x7ff8080400a9 CFRunLoopRunSpecific + 563 5 HIToolbox 0x7ff810b5f254 RunCurrentEventLoopInMode + 292 6 HIToolbox 0x7ff810b5efaa ReceiveNextEventCommon + 587 7 HIToolbox 0x7ff810b5ed48 _BlockUntilNextEventMatchingListInModeWithFilter + 70 8 AppKit 0x7ff80aa24e3c _DPSNextEvent + 886 9 AppKit 0x7ff80aa235e7 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1366 10 AppKit 0x7ff80aa15588 -[NSApplication run] + 586 11 AppKit 0x7ff80a9e97a8 NSApplicationMain + 816 12 dyld 0x11c92d4d5 start + 421

Preflight Panel should give you that warning. View -> Studio -> Preflight

My reaction to the above is, not to worry about "some" members of the community. There will always be someone who will not like this or that suggestion. What matters is that you put forward your suggestions based on your needs/experience and it's up to the Affinity team to pick it up and implement it. This shopping list, however, is quite long. 🙂

Enabling Inline in Text creates an extra character to the left of the graphics. This only appears when the document is PDFed. I'm not sure whether this has been spotted or reported earlier or whether this only happens to me. Attached a short video and the file I used in the recording. EDIT: I should add that I am running macOS Monterey Version 12 Beta. Inline Graphics.afpub strange_chara.mov

Hello @A_B_C, You are absolutely right. I completely missed your initial report. Renaming a Paragraph Style is not reflected in Table Styles and in fact completely disappears from the Text Style list. Funny enough I keep a list of bugs for Publisher and this has been on my list for a long time. So I should have spotted that straight away. This is a long standing bug.

Please remember that Publisher is just a toolbox that is missing a lot of tools. Use a toolbox that has the tools you need. Publisher is not yet ready for long document productions in my humble opinion.

Hi @A_B_C, That's not how table styles work. See below. I hope it's self explanatory. table.mov

Does this happen even if you select Pass-Through option?

Attaching a file may prompt users of this forum to have a look at what's gone wrong with your file.

Hi @MEB, You are absolutely right. This was an elementary mistake from my part. I have both Beta and the Release versions running and I got confused which was was which. Should have double-checked that. Sorry, no issue here. However, the main reason I was experimenting with pinning was the fact that when you tick Keep paragraph together and apply wrap to the object the object in question goes back to where it was. But only if you apply wrap to it. However if you position the object just one line below where the paragraph starts then the object stays put. I have reported it before but it seems that it was only half fixed. EDIT: I have experimented with this further and have realised that the pin must alway be above the wrapped object for the wrapped object to stay in place. I think this is undesirable and unnecessarily limiting. keeptext.mov

Is it just me or 1.9.3 made the floating object pin unselectable/unmovable. pin.mov

And it is. See my earlier post. From the help File: For JSON files, obtained from web/mobile services or database export, only a single top-level array of objects (and values in those objects) are supported; lower level arrays and objects are not supported.

I'm not sure whether this helps but Affinity doesn't parse JSON beyond the 1st level. From the help File: For JSON files, obtained from web/mobile services or database export, only a single top-level array of objects (and values in those objects) are supported; lower level arrays and objects are not supported.

That may be true but that doesn't necessarily mean that all images have to be stored in memory all the time. Good memory management implies that pictures are loaded when they are needed to be shown on the screen and swapped out when they are not needed any more.

Pleases search the forum for the answer. This question was asked time and time again.

That's right. Didn't read the post correctly.

You also need to tick Aloow "Unknown" plugins to be used

Hi @DorothyG Try to re-download it. The file might have been corrupted during the download. It's rare but it does happen.

I didn't watch the whole video, sorry. You may need to experiment a bit to get something similar but I hope you know that Apply Image exists in Affinity Photo too. There will alway be differences between these 2 programs. Affinity Photo is not a clone of Photoshop.