davepmiddleton

Congratulations to Affinity with the acquisition. Affinity has been noticed and rewarded for their decades of dedication. For me personally, I met Ash’s announcement with mixed feelings for the same reasons we can read here in this forum. There a many business examples of corporate acquisitions that involve VC , PE or shareholders where it did not end well for its customers (price hikes, reduced product quality etc.) or its employees (restructuring, lay-offs etc). The problem I had with Adobe in 2013 is that they no longer offered the user a choice: a perpetual license or a subscription-based license. There is a business case for both license models, but Adobe took that choice away from the customer. Therefore I went straight to Affinity and never looked back. I would summarize Canva’s USP as: accessible and affordable design for non-professionals. I see three possible strategies with the recent acquisition: Compete with Adobe: extend the Canva product portfolio with Affinity products for the professional market with desktop apps and exchangeable files. This may be the best strategy for Affinity’s user-base; even better if Canva decides to offer two licenses models: perpetual and subscription. Complement Adobe: integrate Affinity products to offer more design capabilities for the non-professional market. In this case I don’t see the Affinity products survive in their current form and I expect them to become part of the Canva SaaS platform. A subscription will be the most likely license model. Eliminate competition: If Canva considers Affinity a potential future threat, it just acquired Affinity to shelf its products (Like Adobe, Microsoft, Corel, Symantec etc). This is not a likely strategy as Canva would have offered the aforementioned 400M USD instead of 1B USD for the Affinity acquisition. Even if we end up with the first strategy, we as Affinity users, may not be out of the water yet. Canva has IPO ambitions. When public there will be pressure on Canva to offer subscription-based licenses only, because subscriptions offer a predictable cash flow and reduce new development risks. We can only hope it’s different his time.

Had similar issues with performance: every object selection, change etc took about 2-3 sec. with an occasional application hang. Working with Publisher was a real pain. I may have a similar mixed graphics card setup i.e. a Intel HD 630 and NVIDIA GTX 1050Ti. For me this setting works without problems: the renderer is the NVIDIA card, but I had to disable OpenCL.

Via a workaround (a round-trip to e.g. Designer), you can make snapshots in Publisher (see link below). It would be great to enable this feature directly in Publisher.

Very much in favor of a GREP-style feature. This will be a big time-saver. In the latest Publisher version, you still have to manually style for example a lead-in with say the first 2 words in small caps after a drop caps for e.g. every first chapter page. This is just one example for the many use cases for a GREP style feature.

Thanks @Jon P, I used this font: "IM Fell English" to recreate an old book style. The font can be found here: https://fonts.google.com/specimen/IM+Fell+English Will work with Arial and see if the error will repeat.

Created a document with "lorem ipsum" filler text inside a text frame, two paragraph styles and a drop caps to test run the new app before creating a production version. I loaded a Fell Type font using the FontBase font manager. A crash can be replicated multiple times on my machine: Use the move tool (V) and double click anywhere in the text frame; Use Crtl + A to select all text; Publisher will quit without a warning. Probably an issue with the libStory.dll. Luckily, Publisher saved a version that can be recovered. Crash Report attached. Specs: Publisher version 1.7.1.404 Windows 10 Pro version 1903 Build 18362.175, 64-bit. 9afa939c-57d5-4e6d-abc1-4a11baf9985a.dmp

Just found the answer. It is a color profile setting, but not in Preferences, but in the Document Setup. When I set the Color Format to RGB/16 and the Color Profile to sRGB IEC1966-2.1 the profiles match.

I created a color swatch in Designer and created the same swatch in other applications e.g. MS Office and Adobe Illustrator (e.g. to share with others, and for templates). To my big surprise the color in Designer swatches are different compared to Microsoft Office and Adobe Illustrator. An example is shown below for the color swatch RGB value (228,216,179). In Designer the color has a pink/salmon hue, whereas in e.g. Adobe it is a light shade of beige. The latter should be the color close to the color I eye dropped from a photograph. Note that Designer uses the same color profile, sRGB IEC61966-2.1 as e.g. Adobe Illustrator. I use the same monitor to display color for all applications concerned. I am not sure if this is a bug or whether I forgot some (color) setting, but some advice is appreciated on how to achieve a common color swatch among applications. Cheers, Dave