Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for 'scripting'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.3 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

  1. Are there any plans to add scripting support? I notice there is no Applescript library at all but am interested to know if there are plans to add Applescript or perhaps Javascript support. Virtually everything we do as far as creating PDFs, packaging, placing images and text, formatting, proofing, sending pages to print etc is done via script. Tagged text goes hand-in-hand with scripting so I think this needs to also be supported.
  2. Scripting would be very welcome. Scripting Summa OPOS-marks to a design to print and cut without Adobe or Corel software please?
  3. maybe we will get these when we get scripting/plugin support hopefully within the next couple of months.
  4. If you add scripting facility to Affinity products, users could create such simple function on their own. Is this ever planed?
  5. If you know the history of scripting in Photoshop, it initially seems to have been made purely for internal purposes, for quality review, and then a few motivate customers (iirc a newspaper chair, or maybe even Sports Illustrated) championed it even when it was very very not-customer-ready, because they needed a way to in the case of SI) pull together thousands of shots of the same Sunday football match and have it to the press Monday morning. There are still things broken there, but many people get value. I'd think scripting of some sort would open a lot of markets, not just the usual print folks but markets for all kinds of online media that typically are very speed-driven, things like "take this directory of pictures and put the logo and a bunch of affiliated text on all of them, send to PDFs and be ready to send to the printer because they're wedding-album takeaways" etc. Bulk job, simple in concept but lots of clicking and dragging without a script.
  6. Right now, that would likely require having more preference options or yet another menu item to the already long lists. The "art of programming" also involves finding the right balance between "infinite customization" and "stiff defaults". In my opinion, Affinity apps do maintain a pretty good balance here. Whereas apps like GraphicConverter or VectorStyler are examples of apps that massively suffer from Featuritis™ and Preferentirrhea®. I use both for some of their specific niche features, but having too many options and preferences actually doesn't always make them more usable for me. We're eagerly waiting for the already announced scripting!
  7. Of course there are programmatic ways under macOS to detect how many monitors are connected and to react on newly connected or disconnected monitors, thus also triggering external monitors. A bunch of macOS third party apps do handle this in a graceful manner. Further one can also easily deal with that via scripting if wanted, just one two simple AppleScript examples here … https://apple.stackexchange.com/questions/333556/how-do-i-trigger-a-script-when-a-second-monitor-is-attached
  8. Sorry, this feature doesn't exist. Perhaps we'll be able to do it someday when we have scripting. Cheers
  9. Sorry if I said something wrong in your application but I am new at trying it and that's what I found if there is something that I said was wrong please tell me how to use it Effects envelope distort effects Image Trace effects distort & transform effects Tools vertical type tool Rectangular grid tool polar grid tool Scripting Panel
  10. I agree, best would be a DAM which keeps the folder/file structure intact and shows "unknown" files as is. only other solution I know of is the file manager XYplorer but thats usually coupled with a lot of scripting and elbow grease to make it do what you need. https://www.xyplorer.com/index.php https://www.xyplorer.com/xyfc/viewtopic.php?t=18442
  11. What you want is scripting capabilities + an API for Affinity Photo. The Serif Team has posted this; In other words; the Capture One Developers can do it themselves once the scripting feature is available.
  12. You can assign shortcuts for Find Next and Find Previous. But those work only after you have pressed Return or clicked the Find button to start the actual search. On Mac, it should be possible to "click" the buttons via UI scripting, i.e. by utilizing some accessibility features via AppleScript's System Events. That can be run as Automator or Shortcuts plugin or with e.g. Keyboard Maestro, each by using keyboard shortcuts. I've posted a bunch of similar UI scripting examples here in the forums already: https://forum.affinity.serif.com/index.php?/search/&q=system events&quick=1&author=loukash&search_and_or=and&sortby=relevancy
  13. Hi, coming from Photoshop, there are a lot of cases where scripting is helpful. Still hoping to see that in the future, there is this case that I had in Photoshop solved in different ways that I did not find a solution for in Affinity: I need to batch export layers. So I have a mildly complex setup of a composition, with a few layers that change in every exported image. Could be for example a few font layers that are available in different languages, so instead of manually switching layers and saving a new export each time, this could be solved by a script or a batch that switches through different layer states and saves afterwards (both works in photoshop). Photoshop even has a feature called save "Image Assets from Layers" which does something similar but much easier: by just naming the layer with a .png or .jpg at the end. Now: In Affinity neither Macros, not Scripting (not available), nor slices (not saving the rest of the composition), nor layer states (no batch processing for that), nor ... is capable of helping here. Having just bought V2 because layer states (as layer comps in PS) are now available, I am disappointed that the main reason I upgraded is not even possible. So the layer states are almost useless ... Will there be something soon to enable efficient workflows? Or is there a way already? How about a doc for writing a plugin? Thanks hOSHI
  14. Hi, Newbie here. Wish to purchase software, but before I make the jump, can you help me out with what the scripting options are. I think I read in the forum, scripting was talked about 4 years ago. I am wandering what progress has been made on this front. It comes across, as there still might not be any scripting integration. If there are plans to introduce then a timeline and what language etc, would help, to help me decide my purchase. Many thanks
  15. How would that work? Do you just mean to export an individual story? From a DTP perspective HTML is essentially an eBook/ePub format, which has already been requested in other threads, such as: Alternatively HTML could be a simple rich text format for exporting an individual story, which would be a different feature request from what people are usually asking for. Either way, this is not the correct place for this - the thread this was posted in is about scripting. If you are looking for the ePub style export of HTML, you should add your support in an existing thread for that. If you are looking for a story export, there may be an existing thread requesting that but I am not turning one up in my initial attempt at searching. If you meant something else by a text format export, I have no idea what that would be, but I would suggest searching for an existing thread and creating one if you can't find it, giving a bit more detailed of an explanation of exactly what you want from it.
  16. Thanks for the work you are doing on this. I want to help you make a product that will be seen by others (and myself) as being very useful and I think one of the very best places that scripting should be designed for is time savings and batch processing. I have hundreds of articles that need to use the exact same template. I need to be able to swap out the template on every one of them, and then click a button to recreate PDFs for them all. Can scripting do this? It should. Failing this type of usefulness, scripting is of very little value to me. And I would say probably of very little value to others, as well. "Batch processing is it" when it comes to scripting. Please don't forget batch processing. Otherwise, affinity publisher cannot serve me in the end. Thank you.
  17. The link about scripting support makes it very clear that the demo is not how the Affinity suite will run scripts and plugins; that it is "all VERY early, like pre-pre-pre-alpha," there is not even any timescale for its release, & so on. So about the only thing newish that is revealed about it is that in its 'pre-alpha' state it can run Javascript code. Better than nothing I suppose but the demos don't reveal anything specific about what we will actually be able to do with scripting when it finally makes it into Affinity, or how long we will have to wait for that.
  18. Do you have a link for that? I have not seen anything about it. What specifically have we not known about them working on for years? Scripting support was first mentioned at least 4 years ago when they mentioned that they had not at that time decided what scripting language it would be based on. I am not complaining about anything, just reiterating what they have said in the past about the reasons they do not discuss any specifics about their plans for the future.
  19. Only the Serifairies Of Nottingham know… You're not! I'm attempting to learn scripting since over two decades, and I still feel I'm too stupid for it, too! It's just my unbroken will to eventually score a victory that makes me spend nights trying to figure out a task that would otherwise take a second if I would just click that silly button!
  20. Hi loukash Thank you very much for the tip! You can assign shortcuts for Find Next and Find Previous. But those work only after you have pressed Return or clicked the Find button to start the actual search. This works quite well, but: Do you have any idea why Serif has not provided a shortcut for replace? After that I would have nothing more to complain about! As far as UI scripting is concerned: I'm too stupid for that!
  21. The last big update to V2 was mainly under the hood things with the promise that would enable new features. So we wait and see. Scripting is being actively developed.
  22. Serif has just started its Black Friday sale so you can upgrade now from V1 to V2 for £71.99 which covers all apps on all platforms and is traditionally the largest discount you get throughout the year. It's possible that macro keyboard shortcuts will come in the free V2 updates and also scripting (which we know they are working on) but there is no guarantee on any of that. It's a bit of a gamble but V2 also has lots of additional features, bug fixes etc that it may be worth upgrading now to get the discount rather than missing out and then find they add the shortcuts in the next free update for V2 users and you have to pay the full price at that point in time. https://affinity.serif.com/en-gb/store/upgrade-offer/
  23. @Frozen Death Knight We may have to wait a while for scripting to come to beta and then we will have more info about the controls for them. Hopefully we will know soon in what version it will become available.
  24. Appreciate the work. Just to let you know that my ability to use Affinity Publishing is "do or die" based on Scripting. I need to be able to 1 - swap the same master page into 100+ documents at once 2 - save "text version" of 100+ documents at once 3 - save "html version" of 100+ documents at once 4 - generate PDFs of 100+ documents at once This will allow me to drop InDesign. Speaking of which, it seems that "save as text" and "save as html" are currently not available? Therefore, that is a feature request, as well. Otherwise, I am still bound to InDesign (which I don't want to be). Thanks!
  25. Hi, I can't find answers to this question on the affinity website, so I'd appreciate any guidance. I'm a developer using Affinity Designer for artwork creation for a game. I have a bunch of assets, and I need to separate out the various named layers in the assets into different files for 1x, 2x and 3x, so they can be layered back together in the game. I also need to do some simple operations on export, like applying filters, setting fill colours...etc. The thought of sitting down and performing the monotonous task of hiding layers, setting properties and clicking export for potentially hundreds of files is daunting, and I'd like to avoid a manual task wherever possible. Obviously my initial thought as a developer is that surely this is scriptable - I should be able to write a simple Python script (or AppleScript), that could automate the process quite easily. I had a quick search around the .app bundle on MacOS, and couldn't find the the sdef Scripting Definitions file, so I guess AppleScript is not supported, but I can't imagine a professional app like this wouldn't support something like Python? Is there a scripting API that will allow to me to execute simple editing and export steps on a batch of layers? If there is, could someone point me in the direction of the documentation? Thanks! -Matt
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.