Seneca Posted April 13, 2021 Share Posted April 13, 2021 Is it just me or 1.9.3 made the floating object pin unselectable/unmovable. pin.mov Quote 2017 27” iMac 4.2 GHz Quad-Core Intel Core i7 • Radeon Pr 580 8GB • 64GB • Ventura 13.6.4. iPad Pro (10.5-inch) • 256GB • Version 16.4 Link to comment Share on other sites More sharing options...
Staff MEB Posted April 13, 2021 Staff Share Posted April 13, 2021 Have you expanded the filler text (menu Text > Expand > Expand field) before pinning the object? Quote A Guide to Learning Affinity Software Link to comment Share on other sites More sharing options...
loukash Posted April 13, 2021 Share Posted April 13, 2021 1 hour ago, Seneca said: Is it just me It is just you, but… 10 minutes ago, MEB said: Have you expanded the filler text (menu Text > Expand > Expand field) before pinning the object? … but while I was testing what happens with filler text in non-editable mode and then switch back to editable, I've managed to crash APu while doing so: Process: Affinity Publisher [57680] Path: /Applications/Design/Affinity Publisher.app/Contents/MacOS/Affinity Publisher Identifier: Affinity Publisher Version: 1.9.3 (1.9.3) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Affinity Publisher [57680] User ID: 501 Date/Time: 2021-04-13 22:40:14.999 +0200 OS Version: Mac OS X 10.11.6 (15G22010) […] Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0x18: --> __TEXT 00000001080eb000-000000010812f000 [ 272K] r-x/r-x SM=COW b4\ � [/Applications/Design/Affinity Publisher.app/Contents/MacOS/Affinity Publisher] Application Specific Information: objc_msgSend() selector name: imageForSpreadAtIndex:childlist: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib 0x00000001427544dd objc_msgSend + 29 1 com.seriflabs.libcocoaui 0x00000001137a5890 -[SpreadLayer drawInContext:] + 128 2 com.apple.QuartzCore 0x0000000117435a05 CABackingStoreUpdate_ + 3494 3 com.apple.QuartzCore 0x0000000117434c59 ___ZN2CA5Layer8display_Ev_block_invoke + 59 4 com.apple.QuartzCore 0x0000000117434645 CA::Layer::display_() + 1565 5 com.apple.QuartzCore 0x000000011742638d CA::Layer::display_if_needed(CA::Transaction*) + 603 6 com.apple.QuartzCore 0x0000000117425eb5 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 35 7 com.apple.QuartzCore 0x0000000117425389 CA::Context::commit_transaction(CA::Transaction*) + 277 8 com.apple.QuartzCore 0x0000000117424fd4 CA::Transaction::commit() + 508 9 com.apple.QuartzCore 0x0000000117430863 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 71 10 com.apple.CoreFoundation 0x00000001441ddfc7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 11 com.apple.CoreFoundation 0x00000001441ddf37 __CFRunLoopDoObservers + 391 12 com.apple.CoreFoundation 0x00000001441bce48 CFRunLoopRunSpecific + 328 13 com.apple.HIToolbox 0x000000014c628935 RunCurrentEventLoopInMode + 235 14 com.apple.HIToolbox 0x000000014c62876f ReceiveNextEventCommon + 432 15 com.apple.HIToolbox 0x000000014c6285af _BlockUntilNextEventMatchingListInModeWithFilter + 71 16 com.apple.AppKit 0x0000000142ca4df6 _DPSNextEvent + 1067 17 com.apple.AppKit 0x0000000142ca4226 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 18 com.apple.AppKit 0x0000000142c98d80 -[NSApplication run] + 682 19 com.apple.AppKit 0x0000000142c62368 NSApplicationMain + 1176 20 libdyld.dylib 0x00000001460b55ad start + 1 […] Model: MacBookPro9,1, BootROM 421.0.0, 4 processors, Intel Core i7, 2,6 GHz, 16 GB, SMC 2.1f175 Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020 Quote MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2 Link to comment Share on other sites More sharing options...
Seneca Posted April 13, 2021 Author Share Posted April 13, 2021 2 hours ago, MEB said: Have you expanded the filler text (menu Text > Expand > Expand field) before pinning the object? 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 Quote 2017 27” iMac 4.2 GHz Quad-Core Intel Core i7 • Radeon Pr 580 8GB • 64GB • Ventura 13.6.4. iPad Pro (10.5-inch) • 256GB • Version 16.4 Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.