In my perspective, V1 had support abandoned 4 years ago with me when I bought it, why do you think them introducing V2 changes that? If they’d just fix things instead of continually adding new features I’d have a much different perspective.
#Affinity photo macros ipad upgrade
There hasn’t been an actual “update” that I needed to V1 in 4 years - what’s your point? Every release they’ve made has been an upgrade of new features with nearly zero updates to existing ones that have bugs. You act like you think I believe that’s a problem? Keep adding features to lure the sales - but do as much as you can to hide the bugs and defects don’t spend a lick of time fixing anything unless it prevents you from adding one new feature. I’ve come to the conclusion Serif is just a company that markets software. The most that was done was being marked as duplicate with nothing further done. Not a single one has been fixed or addressed over the last 4 years that I’ve owned the software. I’ve opened about 5 tickets with Serif (which ultimately were duplicates). I’ve actually opened tickets with Adobe on a number of occasions and had every single one addressed and eventually fixed. There’s just too many fanboys basking in the low price and lots of “free new features”.Įach release adds more “free features” I didn’t want or expect. Scripting in particular, though worth looking forward to, I agree can never and should never replace proper Macro functionality.Serif is quickly heading in the same direction. There's been some very good discussions with staff there. Either way, a macro facility is present and scripting is in the pipeline. There's still preexisting bugs and it's been said they need more people. So basing one's review on currently available features is the best call. We know nothing about future development and we can't know. We don't know whether the changes will even be big or even small, whenever and if they do occur. All that said, I don't see a premise behind saying "in the future it'll be possible". Adobe is more likely the real outlier in that they've had decades of experience to build a proper foundation for their API and Actions panel. Export Persona does cover some of those gaps for single file operations. Not that I don't run into similar limitations in other apps.
I prefer to use them for housekeeping tasks, but some of what I would typically do in other programs I can't setup a macro for in Affinity. It's discouraged me using them more faithfully, but I do utilize them. There's limitations with regards to what Macros can do that I seem to find whenever I go to set one up.
And of course the Macro facility has to be enhanced, since in it's actual state, as already said, it's pretty limited in overal functionality. Where the later (Macros) can't add functionality not already available or accessable in the app GUI so far. In short, Scripting is like programming offering much more flexibility, where Macros in contrast to that are more like clicking a GUI workflow together. Further for example, a script could call and execute some available macro, or vice versa. Though some of these things could also be made available & reusable in/for Macros then too. etc., aka allowing to do a lot of things so far not available in Affinity apps. Scripting usually offers by far a lot more than Macros, like looping, conditions, calling/using/adding external functions, I/O pipes. but in your post it sounds like you suggest scripting is supposed to be the solution for a limited macro feature.ĭepends on how it is implemented and what it finally offers. If it ( a scripting facility) would be instead implemented like/after the Macros facility, then it would be probably crappy. Meaning, it should then ideally also offer some CLI based access to Affinity apps objects/methods/functions (.so not been restricted to only/just being exectable inside the GUI with all that app GUI mem overhead), further it should offer some real debugging capabilities. There's also no real possibility to single step through, or halt a macro via some stop breakpoint etc., so no debug features.Īll in all the overall hope here lies more on some additional future Scripting capabilities for the Affinity apps, as far as it's good, flexible and powerful implemented. Also things like nesting macros, or the interoperation of macros, aren't really possible, or are only possible via some cumbersome unpleasent copy/paste workarounds. There are a bunch of things missing or which Macros doesn't offer and can't do, especially in terms of document size independent dynamic handling, I/O file support, text and layer handling. The APh Macro capabilities have always been and are sadly pretty limited, if not to say very weak. For me, this is also important and this is not in the new version.
0 kommentar(er)
