taharvey

Indeed. Its is more important to maintain in-system consistency, then cross-platform consistency. I use 50 different applications on a regular basis, its not worth anyone of those apps dancing the jig, while other are doing the waltz. Its at best annoying, but mostly unproductive. It's not worth debating which is your favorite way. On the Mac, there is effectively only 1 way to drag copy. Just do it.

Thats fine too. Just pick one way. Not both ways. It is inconsistent behavior.

I've been having a problem with... Publisher crashing incessantly. (MacOS) My Graphic designer is about to throw in the towel and go back to inDesign. I'm giving it a couple days to see if there are responses from the team here on solutions. 1. Randomly certain file links will cause Publisher to crash. You can rename the file, then relink it, and it will "magically" fix it. But then another link will cause the same problem hours/days later You can rename the whole assets folder, then re-find it, which can fix all in one operation, or just cause it to crash forever. Depending on your luck 2. When re-finding the whole assets folder, all the assets relink, but they stay as low-res stand-ins until you manually relink each and every file... Currently since Publisher clearly has serious file management bugs, I've embedded everything. We'll see how long it can keep from imploding. What is the solution to both 1 & 2, and what is the timeline for bug fixes?

I've been trying not to judge, but a year into using Affinity, the key bindings often make no sense. I don't know where your key bindings derive from, but many common ones are opposite every program I've every used... Adobe, Every MacOS app, the old Freehand & Macromedia stuff. Why be crazy? Why not use standard key bindings? It's a huge productivity suck. Duplicate: Option-drag, not Cmd-Drag. (This is universal: every program I can think of on the Mac is option-drag). The command is already is reserved territory fo, well... Commands! Because you overload it, drag duplication is crazy making. Every time I press command to execute a key binding while dragging... it copies the object! Resize around centers: Option-drag, not Cmd-Drag. Again this almost universal. Please... do not overload the Command key bindings. Constrain aspect ratio: Affinity has non-locked aspect-ratio when dragging a corner... but opposite behavior with images! Consistent UX expectations is more important than which behavior you chose. Pick one way: Adobe defaults to unconstrained, with shift adds constraints. Omnigraffle, Pages/Keynote, are default constrained, with an unlock constraint button, but you could use shift in reverse.

To be clear. I am a software architect. This is no illusion, it is in fact the way it works. And no, it is not a "performance nightmare". But yes, it does optimize by using time coalescing so there aren't millisecond changes to disk. That said, you can watch the update rate if use turn on sharing with another person. The updates to disk, or even with latency a full round trip disk->cloud->disk in sharing, are on the order of less then 200-500 milliseconds... fast enough that there is effectively no loss to any lack of save or crash... ever.

It think you misunderstand the underpinnings in the software. It ALWAYS saves... with every character stroke even if the file has never been saved... IF the application is fully native coded in the Cocoa framework. Yes, common applications built on external frameworks don't do it (Adobe, Microsoft), but "Built For MacOS" applications do... always (Omnigraffle, Pages, Numbers, etc) I've never saved a Pages file in 10 years, and 1000s of pages of documentation... Every time I open the application, for even unsaved files, there I am right back where I left it. Never experienced a loss of data. Yet MS Word crashes a loses data even when continuously saving.

As a Mac user... "save" feels very 1990s. Most of my applications are "stateless", meaning there is no difference between the memory state, the undo history, the file, and cloud versions. It is a all a continuous stream. I rarely think about "save", crashes, on, off, sleep... the file always is exactly where I left it. Save feels kinda retro. But on this topic, native Cocoa applications continuously stream to the disk too. That said, they handle collisions gracefully. In fact if I pull up a file that one of my employees is editing, our applications continue to work, by save out: "filename - changed by joe blogs on X/X/X date"

One of the real big missed opportunity in the Linux market is an OS is (A LOT) more than a Kernel. But Linus, has little interest beyond the Kernel. Windows, and even much more so, the MacOS offers a very complete framework with strong development tools to back it. Each of them well integrated and pre-tested, with symmetric APIs. What I've noticed in the Mac market is 1 programmer can readily pull off a well polished application, where in the Linux would it take a large team... with worse results. QT isn't even a fraction of the scale of the MacOS frameworks. On Metal. First, Metal was 2-3 years first to market before a similar open source library (Vulkan) was available. Should Apple wait for committees to catch up, or just innovate ahead? Second, just like Nvidia has Cuda, Microsoft has directX, Apple has Metal. People never give Nvidia a hard time for Cuda, so why complain about Apple? It turns out Apple is the largest GPU manufacturer in the world today, delivering 200-400 Million iPhone GPUs per year. They want to control their technology destiny like everybody else..

Is there any way to get the Beta version again? Our is expired. We have a file that was working fine in Beta. But now blows up in release version, right at launch. F@%K! Need to finish the project. I'm going to get thrown under the bus for choosing to use Publisher instead of tried-and-true software like Indesign. Help!

This is disappointing. Very unMacOS like I've got a problem now, because Publisher crashes all over the place. Trying to copy out the pages 1-by-1 until I can track down the problem. But no way to copy-paste

This ongoing thread cracks me up. There isn't a real linux desktop market, and its very unlikely to evolve, for multiple well-known reasons. Even Linus has long ago dismissed that the "year of the linux desktop" will ever come. Linux dominates the embedded and headless server space, but isn't a compelling market for users outside of a few developers who don't come up for air above the terminal-editor level. The very culture of the linux core audience, keeps it from developing a canonical full-stack framework and singular OS distro, high quality UI/UX, or attract the non-programmer designer and business talent to ever make the market successful. Anybody who is betting on a linux market to emerge for consumer software is kidding themselves. Hasn't happen in 25 years, no indicators that the market changing.

Mojave. Latest. File is 230MB. A dozen art boards.

I just had an issue, that exposed affinity's (very) bad handling of file collisions. There are many things that come up in Affinity that reveal that it is not built on a Cocoa-native framework – but this is the worst so far. I saved a changed a shared file (dropbox) that my employee had also changed. Affinity gave me a dialog box that said the file had aready been changed, and it was deleting my (4 hours) of changes. YIKES! Whenever this happens in other Mac applications, the dialog give you the ability to "save as...". Or it saves, and appends the person and date to the name to make it different, Please fix.

I'm having a problem in Designer. When I start Designer from scratch the Search Field in help as expected in any MacOS application. But when I load some files (Big Files?), the search field disappears and won't come back. This is a frustrating problem. (BTW This is an awesome feature of MacOS, cause you can use the search as a "command line" for functionality you know exists, but don't know where it is in the menubar.)

Generally Agree there. Those are apps that don't get the UX love they need, but we use them anyways... cause what else are you going to do? My PADs software doesn't look that much different from its 20 year old DOS version. Talk about slow velocity. Most serious board designers still don't use auto-routing. What? Crazy! Auto-routing is the quintessential machine learning problem, and yet it hasn't received much development effort over the last 20 years. Total nuts, and very lazy. It is a reason I like the Mac ecosystem though. Strong community commitment to quality. I think a lot of the cruft in these applications has to do with lax community standards for quality. Largely because a poor leader (Microsoft) who has struggled to value design in UX or in architecture, and APIs. Which only makes it harder to build quality applications on these platforms.