robinp

The form of the icons are identical. Even the design of the illustrations are very similar at a glance between designer and photo. The angles are identical and several of the lines are in the same positions. Coupled with the identical tone (not hue), it is impossible at a glance to identify which is which. A longer look and it is obviously possible to identify the pen vs the lens design. But not at a glance. It is terrible design. Ironic.

Thanks. I did send a link to the PDF above but it ended up embedding it. Glad you managed to find it and that a fix is coming.

Here's an example. BTW, the drag and drop upload isn't working on the forum. I had to go through the dialogue to get this to upload @MEB What you're seeing on this video, is the Text Frame panel on my MacBook Pro built in display. The Publisher document is open on my 27" external display. It is repeatable. Screen Recording 2020-02-12 at 11.21.59.mov

Well, given the lack of interest from Serif about this and, it seems, unlikely that it will change any time soon, I've modified the icon colour manually. I think it is much more clear, much more accessible. Slightly concerned about copyright otherwise I'd share it here. Maybe if someone from Serif can give me the go ahead, I'll share what I've done? I can even include the ICNS file for macOS. @MEB

It would be very helpful to be able to set specific elements to not create text overflow warnings. For example, the other day I was making a flow diagram and the standard style I set up had a lot of padding around the text. Some of the boxes I wanted to make more compact which I did by reducing the frame. All the text was still visible but because the padding extended beyond the frames it flags as an overflow. With no ability to quickly zoom to offending frames, there is no way of being 100% comfortable exporting when it comes up with a generic warning about overflowing text. Being able to set these frames to not create overflow warnings would solve this. I'm thinking a simple check box in the text frame settings.

I've been having problems with a placed PDF. For some reason it loses the images that are on the front. Other pages of the PDF seem to be OK. How it should look: How it looks when placed:

I keep finding unexpected behaviours when working with an external display plugged into my MacBook Pro. I really get the feeling that perhaps not much testing has been done on this or similar set ups. This applies to all three apps if I'm honest. Just the most recent example was one I experiences with Published. Often popup windows or panels appear on the screen other than the one being used. The latest one was that the text frame settings panel appeared on my MacBooks display rather than the external one I was working on. I tried to adjust the colour using the colour wheel but the colour would not change. I moved the panel to the same display as the one being used for publisher and immediately it started working. Interestingly, when then moving the panel back to the MacBook display it carried on working as expected. Another recent one was the other day I was using Designer and on one display the artboards started showing as much smaller than they should be, with the artwork appearing to incorrectly extend far beyond the limits even though. Moving the window between displays and then back again resolved this issue. Could they be related?

Hi @Gabe Thanks for getting back to me but it was three weeks ago and I'm afraid I now cannot recall which files were causing the problems. I'll have a go again and see if I can recreate it but when I was doing it, it kept happening over and over again. With regards to the opening vs converting, my point was that it would be much easier to give the user the option of using it as though it had been opened rather than converted. I don't think end users really worry about such subtleties, we just want it to work quickly and easily with the interface getting in the way as little as possible. So whether the file is actually being opened or actually converted, I think it would be helpful to offer the option to open and save PDFs without going through this palaver. While the current implementation may be by design, I struggle to see how it is of benefit to the user. It may make sense to a programmer writing the code behind it, but for the average user this differentiation is somewhat forced and just makes the workflow clunky. Robin

All the reasons for not being more up front about things come back to the idea that their customers are really stupid. That’s not a great look. From my experience, you tell people honestly and thoughtfully what is going on, why something is happening or not and they are pretty good about Understanding it. What people absolutely abhor, is being managed like small children, especially when they are putting in quite a lot of time and effort to assist with the discovery and squashing of bugs.

Not sure if it is connected or not, but there is another, softer crash that occurs when when opening PDFs by dragging them onto the designer window. For example: Open a PDF via dragging it onto the designer icon, or via the open dialogue. Edit the file Export to save the file back to PDF Close file (but not designer) Drag a new PDF onto the designer window that is still visible despite there not being a file open At this point nothing happens. If you then try to open a file by, for example, dropping it on the designer app icon, it opens but then you cannot do anything. My hunch is that the dialogue that appears when opening a PDF doesn't properly generate when opening via dragging a file onto the designer window. It is like it is waiting for an interaction but without any pop up window visible. The only solution I've found is to force quit and start again.

Not when replying specifically to an individual unless you make it clear that it refers to a wider group. Especially when highlighting that their use is not the same as a universal use. If you had meant a wider group you would or, perhaps, should have said. Is this really going to become a debate about semantics?

This is the crash report that macOS created: panic(cpu 0 caller 0xffffff7f962d035a): "afpfs_getnewvnode: orphaned vnode (data)"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/afpfs/afpfs-663.60.1/Sources/afpfs_vfsutils.c:178 Backtrace (CPU 0), Frame : Return Address 0xffffff8202a7ada0 : 0xffffff8011f3bb1b 0xffffff8202a7adf0 : 0xffffff80120733e5 0xffffff8202a7ae30 : 0xffffff8012064e5e 0xffffff8202a7ae80 : 0xffffff8011ee2a40 0xffffff8202a7aea0 : 0xffffff8011f3b207 0xffffff8202a7afa0 : 0xffffff8011f3b5eb 0xffffff8202a7aff0 : 0xffffff80126d24f9 0xffffff8202a7b060 : 0xffffff7f962d035a 0xffffff8202a7b070 : 0xffffff7f962b1937 0xffffff8202a7b130 : 0xffffff7f962b860d 0xffffff8202a7b1d0 : 0xffffff7f962c15d6 0xffffff8202a7b260 : 0xffffff80121be989 0xffffff8202a7b380 : 0xffffff801216c8ab 0xffffff8202a7b6a0 : 0xffffff801216e956 0xffffff8202a7bcc0 : 0xffffff8012171524 0xffffff8202a7bee0 : 0xffffff80121713c8 0xffffff8202a7bf40 : 0xffffff801259acba 0xffffff8202a7bfa0 : 0xffffff8011ee3206 Kernel Extensions in backtrace: com.apple.filesystems.afpfs(11.2)[0B11E6EA-B995-3B1A-97E0-29810991763C]@0xffffff7f96299000->0xffffff7f962e8fff dependency: com.apple.filesystems.hfs.encodings.kext(1)[ADC2D814-3FCD-307F-8999-F8153470A160]@0xffffff7f93771000 dependency: com.apple.security.SecureRemotePassword(1.0)[35E58F79-B1CE-3C18-9C8A-964E7C2D5249]@0xffffff7f96052000 BSD process name corresponding to current thread: com.apple.appkit Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev Mac OS version: 19C57 Kernel version: Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 Kernel UUID: C3E7E405-C692-356B-88D3-C30041FD1E72 Kernel slide: 0x0000000011c00000 Kernel text base: 0xffffff8011e00000 __HIB text base: 0xffffff8011d00000 System model name: MacBookPro15,2 (Mac-827FB448E656EC26) System shutdown begun: NO System uptime in nanoseconds: 63597623328065 last loaded kext at 63089411168031: @filesystems.smbfs 3.4 (addr 0xffffff7f96368000, size 446464) last unloaded kext at 63250044277178: com.parallels.kext.hypervisor 15.1.2 47123 (addr 0xffffff7f9632b000, size 196608) loaded kexts: com.astro-hq.driver.LunaDisplay 1.0.1 @filesystems.smbfs 3.4 >AudioAUUC 1.70 >!A!II210Ethernet 2.3.1 >!AAHCIPort 341.0.2 @filesystems.afpfs 11.2 @nke.asp-tcp 8.1 >!AGraphicsDevicePolicy 4.5.21 @fileutil 20.036.15 @AGDCPluginDisplayMetrics 4.5.21 >!AHV 1 |IOUserEthernet 1.0.1 |IO!BSerialManager 7.0.2f4 >!AUpstreamUserClient 3.6.8 >pmtelemetry 1 >AGPM 111.4.1 >!APlatformEnabler 2.7.0d0 >X86PlatformShim 1.0.0 >!A!IKBLGraphics 14.0.3 @Dont_Steal_Mac_OS_X 7.0.0 >!AThunderboltIP 3.1.3 >BridgeAudioCommunication 6.60 >!ABacklight 180.1 >!ATopCaseHIDEventDriver 3420.1 >!AAVEBridge 6.1 >!AMCCSControl 1.13 >!ABridgeAudio!C 6.60 >!AGFXHDA 100.1.422 >!AHIDALSService 1 >!A!IPCHPMC 2.0.1 >!A!ICFLGraphicsFramebuffer 14.0.3 >!A!ISlowAdaptiveClocking 4.0.0 @filesystems.autofs 3.0 @filesystems.apfs 1412.61.1 >BCMWLANFirmware4355.Hashstore 1 >BCMWLANFirmware4364.Hashstore 1 >BCMWLANFirmware4377.Hashstore 1 @filesystems.hfs.kext 522.0.9 @BootCache 40 @!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1 @!AFSCompression.!AFSCompressionTypeZlib 1.0.0 >!AVirtIO 1.0 >!ABCMWLANBusInterfacePCIe 1 @private.KextAudit 1.0 >!ASmartBatteryManager 161.0.0 >!AACPIButtons 6.1 >!ASMBIOS 2.1 >!AACPIEC 6.1 >!AAPIC 1.7 $!AImage4 1 @nke.applicationfirewall 303 $TMSafetyNet 8 @!ASystemPolicy 2.0.0 |EndpointSecurity 1 |IOAHCI!F 290.0.1 >!AThunderboltPCIUpAdapter 2.5.2 >!AThunderboltDPOutAdapter 6.2.4 >!UAudio 320.49 $SecureRemotePassword 1.0 >!AGraphicsControl 4.5.21 |IOAVB!F 800.17 >!ASSE 1.0 >!ABacklightExpert 1.1.0 @!AGPUWrangler 4.5.21 >!AHS!BDriver 3420.1 >IO!BHIDDriver 7.0.2f4 >!ASMBus!C 1.0.18d1 >!AActuatorDriver 3420.2 >!AMultitouchDriver 3420.2 >!AInputDeviceSupport 3420.4 |IONDRVSupport 569.3 >!AHIDKeyboard 209 |IO!BHost!CUARTTransport 7.0.2f4 |IO!BHost!CTransport 7.0.2f4 >!A!ILpssUARTv1 3.0.60 >!A!ILpssUARTCommon 3.0.60 >!AOnboardSerial 1.0 @!AGraphicsDeviceControl 4.5.21 |IOAccelerator!F2 438.2.8 |IOGraphics!F 569.3 |IOSlowAdaptiveClocking!F 1.0.0 >X86PlatformPlugin 1.0.0 >IOPlatformPlugin!F 6.0.0d8 @plugin.IOgPTPPlugin 800.14 @kext.triggers 1.0 >usb.cdc.ncm 5.0.0 >usb.cdc 5.0.0 >usb.networking 5.0.0 >usb.!UHostCompositeDevice 1.2 >usb.!UVHCIBCE 1.2 >usb.!UVHCI 1.2 >usb.!UVHCICommonBCE 1.0 >usb.!UVHCICommon 1.0 >!AEffaceableNOR 1.0 |IOBufferCopy!C 1.1.0 |IOBufferCopyEngine!F 1 |IONVMe!F 2.1.0 >!AThunderboltPCIDownAdapter 2.5.2 >!AThunderboltDPInAdapter 6.2.4 >!AThunderboltDPAdapter!F 6.2.4 >!AHPM 3.4.4 >!A!ILpssI2C!C 3.0.60 >!A!ILpssDmac 3.0.60 |IOSurface 269.6 @filesystems.hfs.encodings.kext 1 |IOAudio!F 300.2 @vecLib.kext 1.2.0 >!AThunderboltNHI 5.8.1 |IOThunderbolt!F 7.4.7 |IOEthernetAVB!C 1.1.0 >!ABCMWLANCore 1.0.0 >mDNSOffloadUserClient 1.0.1b8 >IOImageLoader 1.0.0 |IOSerial!F 11 |IO80211!FV2 1200.12.2b1 >corecapture 1.0.4 |IOSkywalk!F 1 |IOUSB!F 900.4.2 >!A!ILpssI2C 3.0.60 >usb.!UXHCIPCI 1.2 >usb.!UXHCI 1.2 >!AEFINVRAM 2.1 >!AEFIRuntime 2.1 >!ASMCRTC 1.0 |IOSMBus!F 1.1 |IOHID!F 2.0.0 $quarantine 4 $sandbox 300.0 @kext.!AMatch 1.0.0d1 >!AKeyStore 2 >!UTDM 489.60.3 |IOSCSIBlockCommandsDevice 422.0.2 >!ACredentialManager 1.0 >KernelRelayHost 1 >!ASEPManager 1.0.1 >IOSlaveProcessor 1 >!AFDEKeyStore 28.30 >!AEffaceable!S 1.0 >!AMobileFileIntegrity 1.0.5 @kext.CoreTrust 1 |CoreAnalytics!F 1 |IOTimeSync!F 800.14 |IONetworking!F 3.4 >DiskImages 493.0.0 |IO!B!F 7.0.2f4 |IO!BPacketLogger 7.0.2f4 |IOUSBMass!SDriver 157.40.7 |IOSCSIArchitectureModel!F 422.0.2 |IO!S!F 2.1 |IOUSBHost!F 1.2 >usb.!UCommon 1.0 >!UHostMergeProperties 1.2 >!ABusPower!C 1.0 |IOReport!F 47 >!AACPIPlatform 6.1 >!ASMC 3.1.9 >watchdog 1 |IOPCI!F 2.9 |IOACPI!F 1.4 @kec.pthread 1 @kec.corecrypto 1.0 @kec.Libm 1

I am trying to edit a series of PDFs to redact sensitive information. Upon completing the edit of one file, I tried to save and not only did Designer crash, it crashed and restarted my whole machine without warning. Connected to this, I am editing PDFs and then trying to save them back as PDF. It is REALLY annoying that it is not possible to edit and save the PDFs without Designer wanting to save as a AFDesigner file. All I am doing is opening, deleting and wanting to save. Instead, I have to open, edit, not save as work progresses and then export to overwrite the original file. It was this clunky workflow that resulted in the aforementioned crash. I was editing the file, hit save and then remembered I needed to export, so I hit the escape key. Designer paused for a few seconds and then completely crashed my MacBook Pro.

I would say the purpose for many users is defeated. It is like having a text editor without a find command. Essentially useless for many people. For us, it is the primary use for a vector art editor. We produce drawings in CAD and then often edit the PDFs for presentation purposes. Our files therefore have 000s of objects, many of which have the same style. Selecting all manually is a non-starter.

Not sure how this is any way relevant to my point.

It was mainly rhetorical, picking up the point from @Mark Ingram about how we've had years of free updates. This is a common argument made but is more whattaboutery than an actual answer. If they feel hard done by for providing free updates, or for that matter, feel like it exempts them from criticism then I think it is really rather misguided. I was trying to make the point that a) we don't get to choose or not whether updates are free or not and, b) that I and many others would happily to get an update that includes this feature. I will continue to wait with my wallet at the ready if needed.

I feel somewhat like many of us have been very patient. Obviously I was referring to it being added to Designer.

Yet it is quite literally, better than nothing which is where we are at and have been for quite some time

I'm intrigued by your definition of straight away. Is it measured in decades?

Where and how do I pay to get this feature added?

If you’ve only recently bought it, I would go for the refund. You’re likely to get that whereas a comment from Serif on when this feature will be implemented is... well... incredibly unlikely based on the evidence of this very long discussion. I’ve come to the assumption that there must be a fundamental flaw in the way they’ve implemented the apps to date which precludes the implementation of this feature. Otherwise, why the hell wouldn’t they have done it years ago. At this point many of us would probably settle for a commitment that it will come with 2.0 and have to pay again for it. At least we would then know!

Interesting. Maybe I'll have another look.

Me too. Also assumed there would be selection by attribute features as well. At this point, I’m now hoping that these are all included in version 2.0 and I’ll gladly pay for the update.

The trouble with Inkscape is it involves installing loads of stuff to make it work. I downloaded it and then decided against it when I realised what needed to be done and how it isn’t really a proper MacOS app.