
nwhit
Members-
Posts
718 -
Joined
-
Last visited
Everything posted by nwhit
-
Hmmmm. Not looking too encouraging. Looks like the MAS version (prefs/settings in Library/Containers) has a very different setup as compared to the Affinity Store versions such as my Publisher and Photo beta (in Library/Application Support). Unless someone knows better, looks like my only route might be to use the prefs/settings from my Photo beta version.
-
Thanks, Walt. I just need to work around the issue of already having the MAS version installed, then adding the Affinity store version. Once I get the settings/prefs set up as before, then I can delete the MAS version (although it's still available to me from the MAS should I ever want to go back). Working through all the many betas this last couple years, APhoto release versions from the MAS simply won't allow Eye Candy plugin to open due to the macOS sandboxing security used in the later versions of Mojave and then newer Catalina. But in every iteration of the many betas, it works fine because the betas don't have the sandboxing required for versions from the MAS. I use EC quite a bit for my clients, so really need it to be working without having to resort to using my ancient Adobe CS5 apps, which I am now relegating to a virtual parallels volume running with the old Sierra OS, which I use for a few other older critical apps. Spending the extra $50 is nothing compared to the time EC saves me producing things for clients. Hoping I can simply download and open the Serif Store version and have my much-refined settings ready to use. One way or the other, still needs to be done, but hoping that it might be easy. I'll read that info to see if it has any answers. Thanks. AND OF COURSE, the real question is, are the pref/settings files the same for both versions so that they can simply be moved??? Hopefully they don't have different formats, items, etc. 😉
-
I'm switching from the MAS APhoto to one I'm buying from the Affinity store in order to avoid issues with sandboxing in Mojave. Does anyone know for sure how to preserve my layout, prefs, brushes, etc.? In other words, does the Affinity version use the same prefs/settings folder/files as the MAS version? Or am I going to have to start from scratch? Thanks.
-
Got caught with the same thing! Needed to do a quick job yesterday and was struggling to get the masks to work! Now I know why!
-
Thanks for the assistance! That's a well hidden method to get a transparent background! I tried that but still no luck. I still get a white background when placing the EPS in either APub or ID. I've attached the ADes file to see if there is a possible problem with the artwork. I have to say that I never had an issue like this back with AI, so am a bit discouraged that something so seemingly simple can be so complex. Again, thanks for the help! Aero 20-yr in UK logo.afdesign
-
I have the same issue. Have a Designer 1.8.3 graphic that shows with trans background, has that set in Setup, but when exported as an EPS, has a white background. I also need to have this file as a usable EPS with transparency. How is that done in Designer? Doesn't seem to work. Aero 20-yr in UK logo.eps.zip
-
[619rc] IDML text frame radius Import not correct
nwhit replied to nwhit's topic in [ARCHIVE] Publisher beta on macOS threads
Looks like this is fixed in beta 1.8.4.663. Thanks! -
TomM1, are you using the Mac App Store version or the Affinity store one? I keep thinking that since virtually all of the betas have allowed EC to work that likely the Affinity store version also would (since it's not having to deal with the stricter sandboxing issues of the App Store software). To me, spending $50 for a new copy from the Affinity store in order to get it to work wouldn't be the end of the world.
-
I can appreciate what you're saying. On the other hand, EC has never had an issue in most all of the betas. Works fine. That does lead me to believe that the issue lies in the Mac App Store version and, as you say, sandboxing. In the release version Mac Bugs forum, a poster did report that EC works in 1.8.3. As was the case in 1.8.2 and 1.8.1. So I guess I am now spoiled enough using Affinity apps as opposed to my antique CS5 apps, it would be worth the extra $50 to be able to regularly use EC within APh. Also hoping that you can support EC in the future. It is a very useful tool and greatly reduces time/costs for our clients.
-
With the release of the new beta, I finally updated my Mac App Store version of APhoto to 1.8.3. Once again, as in the past few releases for Mac App Store, Eye Candy will NOT open at all. I had waited specifically (and patiently) for the new 1.8.4.x beta to be released so that I had an option to still be able to use EC, guessing that the identical problem with EC may likely be in the App Store version again. And sure enough, it is still there. Please, please, please. With 1.8.4, can you finally get EC to open in the App Store release? And if it is simply impossible to get it to work with the App Store version, please let us know so that we can go ahead and purchase another copy via your store. I'm sure I'm not the only one who has the App store version and uses EC (or wants to). As it is right now, unless there is a beta available, it simply does not open in 1.8.3 App Store.
-
IDML imported file has transparency issues
nwhit replied to StevieB's topic in [ARCHIVE] Publisher beta on macOS threads
ID has an Effect called Directional Feather that isn't available in APub, nor is it imported correctly AFAIK. Been a requested feature for quite some time since it is a common effect used in ID. -
Corner Options don't work with multiple items
nwhit replied to Jeremy Bohn's topic in V1 Bugs found on macOS
Agree that this should be sorted out. +1 -
IDML imported file has transparency issues
nwhit replied to StevieB's topic in [ARCHIVE] Publisher beta on macOS threads
Gradient feathering in ID is a VERY useful feature and I also DEARLY wish we could have this in APub. We have a bunch of ID files that have this as part of the layout and from experience it cannot be imported into APub since it isn't supported yet. Hopefully it can be added. -
[168] Bounding box wrong when placing APhoto doc
nwhit replied to nwhit's topic in [ARCHIVE] Photo beta on macOS threads
Thanks. Did that in 1.8.2.174 and it worked. -
[168] Bounding box wrong when placing APhoto doc
nwhit replied to nwhit's topic in [ARCHIVE] Photo beta on macOS threads
Sorry, just tried it and it isn't fixed. I opened the APhoto file in the newest beta/rc, then did a save as. Tried to place in the latest APub beta just now and get the same issue. The bounding box is still a full A4 size. -
[619rc] IDML text frame radius Import not correct
nwhit replied to nwhit's topic in [ARCHIVE] Publisher beta on macOS threads
Still not resolved in beta 619rc. -
[619rc] Text not selectable in X4 pdf output
nwhit replied to nwhit's topic in [ARCHIVE] Publisher beta on macOS threads
Not resolved in RC619. -
(584) idml corner radius not quite right.
nwhit replied to woefi's topic in [ARCHIVE] Publisher beta on macOS threads
Had a similar experience with an idml import on a text frame with rounded corners coming in with the right spec for radius, but the wrong look. Jon just said they are aware and working on it, and if you set the doc's dpi to 72, it will then look correct. Obviously, not a fix, but at least they are aware of the issue.- 10 replies
-
- idml
- corner shapes
-
(and 1 more)
Tagged with:
-
[619rc] IDML text frame radius Import not correct
nwhit replied to nwhit's topic in [ARCHIVE] Publisher beta on macOS threads
Interesting! Yes, hope that can be fixed!