Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

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
    • Report a Bug in Affinity Designer V2
    • Report a Bug in Affinity Photo V2
    • Report a Bug in Affinity Publisher V2
    • Report a Bug in Affinity Version 1 applications
  • Beta Software Forums
    • macOS Beta Forums
    • Windows Beta Forums
    • iPad Beta Forums
    • [ARCHIVE] Reports from Affinity Version 1 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. Added a few Python 3 based scripting tools ... Thinning multi architecture Affinity apps under MacOS via Python to reclaim disk space afthumbs - Extracting PNG Thumbnails from .afphoto and .afdesign files whatFileType - Detects file signatures and tells what sort of file it is
  3. Should be possible with a bunch of equally powerful tools (... like the above mentioned sed, or awk, perl, ruby, python ... and so on) which are all also available for Win platforms if needed. On Win even the Powershell can do mighty things via scripting. - One (as always) just has to know what exactly to do & perform and then to try that out with some of the before mentioned scripting tools, or something the like.
  4. I'm using a Mac, and yeah I used the "Select by fill color" but there are very few objects that are the same color. Thanks for the suggestions though the idea of scripting makes my brain hurt. I think what I'm going to do is wait till the vendor outputs a test piece and we see what it looks like under the lighting conditions in the space. At that point I can let the vendor deal with their converted version of the file. Which may be a PNG.
  5. ADe v1 from MAS APh v1 from MAS APub v1 from the Affinity Store BTW I stumbled about it when performing architecture thinning test runs (stripping out arm64 architecture of Affinity apps). One of my initial Python scripting routines prechecks for executables ... def is_mach_exe(path): if os.path.islink(path): return False if not os.access(path, os.X_OK): return False output = subprocess.check_output([FILE, "--mime-type", path]) return output.split()[-1].decode() == "application/octet-stream" ... and afterwards tries to execute lipo -info on the executables, in order to determine incl. architectures (...here then falsly the ICC files too) via a subprocess, which of course generates lipo errors in this case. - So I had to remove execution permissions for the ICC files. And in order to be sure, also for future possible new Affinity installments to not run into the same trap, I had excluded ICC files generally from the overall file scanning process. So as you can see, even it might not doing anything naughty, it can irritate and stop other apps/processes from operating correctly!
  6. Ah yes, that shows my custom AFlipo tool which does the nearly the same as what Armless does, though in a different usage manner. My AFlipo tool operates only on single dragged on apps instead and it's actual version handles also i386 architectures, since El Capitan can still deal with those. - AFlipo is a takeover (adaption) from my old NeXT times, since it was written originally for NeXTstep/OpenStep. But in the meantime I personally use instead some Python scripting (custom Python3 progs) to do such stripping/thinning architecture tasks, since I like to have overall better output of what certain processing stages are doing and which dirs and files they are actually handling. So to say all the background processing tasks most MacOS apps are hiding and don't show you here when recursively processing all the folders & files inside some given app to thin. For example, when processing/traversing some given FAT architecture app recursively, you have to check all the files inside, aka what are executable mach-o binaries or libs and if they are FAT architecture based executable etc., since you only want to call lipo (let it operate) on those files, everything else doesn't have to be touched.
  7. v2 is a nice update. Unfortunately, palette docking on macs still hasn't been addressed. While the windows version allows two or more columns of palettes to be docked side by side, in macOS only one column is possible. I much prefer the tidyness of docked palettes, and really can't stand the floting ones Would be nice if finally, after so many years, someone took the time to fix this. Would be interesting to know how Serif thinks about scripting. From the perspective of tech savvy users it opens up so many possibilities. Is it ever coming?
  8. Hi, I was wondering if there is scripting or macro support in AD2? ? At the moment, I use AHK to achieve some form of automation, but it's not always reliable. So I am wondering if there is scripting available in AD2 and if not, why not?
  9. I just upgraded to v2 mainly so I can leverage the scripting/extension API when it comes out. Very excited about this news! We are going to see some amazing new things when developers can drive Affinity's awesome engine with their own unique ideas.
  10. I believe InDesign has the same limitation - you have to edit the hyperlink style(s) before printing. Someday when we have scripting, I'm sure somebody will write a script you could run to toggle the style of hyperlinks before printing.
  11. You're aware that you can convert hundreds of text objects objects with just one keyboard shortcut? No clicks necessary. Select all text objects in the document (Select > Select Object > Art/Frame Text) Hide them Duplicate all, keep duplicates selected Unhide the duplicates Convert the duplicates to curves All these commands are accessible in menus, customizable via keyboard shortcuts. No click necessary. Additionally you may want to make use of named objects or layer tags for quick selection of specific objects. You should definitely get a 3rd party macro utility. On Mac, I'm using Keyboard Maestro. While Affinity apps aren't officially scriptable (yet), some script support is available out of the box via MacOS UI scripting. That involves all keyboard shortcuts or selecting menu commands, to a certain limited degree even clicking UI elements in the window. For instance, I'm often using a Keyboard Maestro macro via keyboard shortcut that will click the layer name input field for me, based on my canvas object selection, so that I can type in a name right away, without having to click anything: aff_km_macro_click_layer_name.mp4 Similar macros can speed up your repetitive workflows. Make use of such helpers!
  12. Once there is scripting support (probably Javscript based), scripting becomes more useful as a specific script could then most probably be invoked with appropriate content as input and also location for output. Before that I would use scripting for these kinds of tasks only if there is massive repetitive use for an operation, or if there is already a script created for the task. So typically I'd look for support in graphic apps that can exchange content with Affinity apps, free ones, like Inkscape, if there is nothing else available. E.g., for this task, Inkscape has split text functionality that can separate a Clipboard passed text block by line, word or letter to separate text objects, which could then be copy pasted back to Affinity apps and finally distributed horizontally and vertically as needed. Formatting would be supported, as well:
  13. Affinity V2 does not currently have scripting support but it's something our developers are working towards, as mentioned here.
  14. First, I'd like to say that I'm excited to try out the new features in Publisher. I am super about the new notes options. That held me back from using Publisher in anything but personal projects because I do a lot of long document publishing. Just a note. I still bought v1 and would have still bought v2 to encourage competition with Adobe, and I realize that Adobe has had many more years to develop their software. However, Serif doesn't have to develop every feature requested by users!!! I suggest (and I'm not the first) that Serif offer an API to programmers to provide scripts and plug-ins to extend the functionality of Publisher (and obviously the other apps). This would be huge and would also create a new ecosystem around the software and brand loyalty. No company has ALL the resources necessary to address every user's demands and should be expected to. So, what I think Serif should do is open up the software to coders to offer (at a cost to the consumer... or as freeware if they desire) extended functionality. This is not only a huge opportunity for coders, but also for Serif, too. This is my suggestion and I was hoping v2 would have had this. I haven't found it in the features. So, I reopen the discussion here and urge Affinity to consider this for the near-term. Yours, Nico
  15. The day that we get scripting support I'm going to write a document statistics script, assuming the necessary scripting features are added. It would be a good first script to write. I'll include # of layers in this script.
  16. Of course not. That's why they call it… wait for it: a workaround. … and I'm not questioning that by any means. All I am suggesting is simply what you can already have right now. That may be useful for some. If you have a macro utility like Keyboard Maestro, you can also set up a macro that will arrange your v2 floating windows within a second via keyboard shortcut or menu action. For example, a 4-up is easily possible by using a KM preset, or better by using your own coordinates to leave space for the panels and the toolbars. The only limitation for a 4-up on my MacBook is that the minimal height of a floating Affinity document window is hardcoded to 584 px (duh!) so a 4-up will be more useful on larger displays, not necessarily on mine. Here's a quick 4-up KM macro I just set up while typing this: ade2_km_macro_4up_windows.mp4 This should be also possible via Automator and UI scripting, but that requires AppleScript skills. It won't work that easily in v1 Separated Mode because if you have Affinity's studio panels active, they will mess up the MacOS window hierarchy index… Duh. Sloppy UI programming, Serif. ~~~ Speaking of which: This is an archived v1 feedback thread. As confirmed by Serif staff, there won't be any new features in v1, so there's no point in bumping this thread with further requests. If you're stuck with Affinity v1, workarounds is all you can get.
  17. Oh, if you just want the characters reversed to ease typing into a text then that wouldn't be as hard. It should be possible to write a script for this when Serif adds scripting to Affinity which they've said is in development. I'll give it a try if nobody else does.
  18. Also not an insider, but I'm inclined to believe Serif is regretting how some things were initially written into the programs, otherwise RTL would've maybe at least been in the oven by now. We were told it would be quite a bit before it's added in. This admission already came due to many users like yourself, @mehdy, had noticed it was still missing in V2. So you are definitely not alone as many others have also requested this feature. In Twitter, they have said it would require a rewrite of the text engine, but we don't know the details other than it would take a "long time". They have mentioned they are working on adding in scripting as well, an MSI installer and fixing a multitude of bugs, so we truly have no idea when any other features will be addressed.
  19. This is to shed some light to darkness... I share this to help present Adobe users to be able to deal with misinformation that is spread on the Internet, also on this forum. Whenever spot swatches are used, they typically have a reference to the library color (so that their meaning is clear whenever separated for print). It is a simple matter to reassign colors to them (in case their original color representation is broken). The color representations do not need to be accurate but the following video clip shows how sRGB representations can easily be picked by using the PANTONE Connect Plugin also when using a free PANTONE account: dontpanic.mp4 Missing non-spot colors would simply just be resolved to their standard composite colors. The files containing library spot colors can still be placed and exported for production even without proper color representations (dependent on missing libraries), so they would be shown in grayscale e.g. in InDesign and Adobe Acrobat: I hope this helps to get a bit firmer grasp on what the notorious PANTONE change means. As mentioned, most users probably just continue using legacy libraries (they were warned about the forthcoming change for about a year before it happened and should accordingly have realized to create backup copies). The legacy libraries will most probably be available from various other sources, as well, some of which no doubt a bit dodgy. But as shown, the missing representations can be retrieved in sRGB relatively easily, and without extra cost. The mapping might become easier once there is a proper PANTONE plug-in. Scripting tools could also be used to automate the task. UPDATE: In addition to what is said above, it should be noted that all pre Nov 22 created Photoshop files with PANTONE colors will open non-disrupted in Photoshop post Nov 22 versions (so the disruption will only affect Photoshop files with most but not all PANTONE book colors used in Photoshop files created in post Nov 22 versions). So the situation demonstrated above on the video would not happen when opening a PSD file containing these colors in a file created in pre Nov 22 version of Photoshop [I confirmed this with one created in PS2002 and CS6], even when opened in a Photoshop version dated from Nov 22 or later that no longer ships with .acb libraries. Similarly all InDesign and Illustrator files containing swatches from PANTONE color books will open and are placeable as before, without disruption. In a nutshell this means that disruptive behavior has been reduced to the minimum. https://helpx.adobe.com/photoshop/kb/pantone-color-books-photoshop.html https://helpx.adobe.com/illustrator/kb/pantone-color-books-illustrator.html https://helpx.adobe.com/indesign/kb/pantone-color-books-indesign.html
  20. See full size exhibit in the attached [Added GM b120322 PDF versioning ability made no difference and AfPub2 still choking on fonts.pdf] See the test PDF file that was used in these AfPub2 experiments [Mapping Epping Base Line - Overview Epping Base Line Monuments.pdf] Windows 10 Pro, Global Mapper Pro v24.0 (b120322), scripted PDF export; Today's build of Global Mapper v24.0 (b120322) fully supports embedding special fonts such as Myriad Web Pro Condensed as well as explicitly defining Adobe PDF formatting versions - see attached example [Mapping Epping Base Line - Overview Epping Base Line Monuments.pdf]. Huge thanks and much appreciation to Mike Childs in particular, and to Blue Marble Geographics for exposing these new commands to Global Mapper scripting. Issue 1 - AfPub2 can't seem to recognize the PDF correctly, although Acrobat Reader does: Issue 2 - AfPub2 appears to have problems in recognizing the embedded font, but only after the "Fix" (passthrough to interpreted). Ignoring the preflight warning and exporting the PDF anyway from AfPub2 didn't appear to corrupt the embedded fonts Added GM b120322 PDF versioning ability made no difference and AfPub2 still choking on fonts.pdf Mapping Epping Base Line - Overview Epping Base Line Monuments.pdf
  21. Speaking from experience with scripting CorelDRAW, this is likely to come back and bite us at some point in the future, namely when scripting is added. Reasoning: It's not uncommon to script operations on groups selected by name or by Z-position in the layer stack. If you can't create a group with exactly one object, then you can't apply the same script that you would normally apply to a group. In some cases, the user could set things up with a layer instead of a group (there is no requirement to have more than one object in a layer), but this is not always possible, especially when scripting a serious of operations that may move and/or create objects between layers.
  22. Lua and JavaScript are both popular scripting languages used in various software development projects. However, in the context of photo, design, and art based software, Lua may be a more suitable choice for some reasons: Lua is designed to be small and efficient, making it well-suited for use in resource-intensive applications such as image and video processing. Lua has a simple and easy-to-learn syntax, which makes it easy for designers and artists to write and maintain scripts without needing a computer science background. Lua has a built-in garbage collector, which can help prevent memory leaks and other performance issues that can occur when working with large image and video files. JavaScript can be less efficient than Lua and it can be slow in certain situations. JavaScript is also a more complex language, which can make it more difficult to learn and use than Lua for non-technical users. There's a reason why LUA is used in World of Warcraft. Computers with less processing power can handle LUA better.
  23. My issue #2 seems to be complicated by changes in Preferences by Affinity and Apple. First, note that in Ventura the main App menu now lists Settings not Preferences, but once you open the Window in Affinities App, it is still titled Preferences. Next, the Preference settings offered differ between Publisher and Designer. AutoCorrect settings do appear as a Level 1 heading in Publisher (and turning off Autocorrect there does solve my problem with double subscripting in Publisher). BTW, note that search in Preferences is case sensitive: "AutoCorrect" works and "autocorrect" does not. Wouldn't have expected that... But, in Designer, I still can find no place to control AutoCorrect settings. Hopefully, this is a bug somehow, since it clearly belong in both Apps. Curiously, in Designer v1 Preferences, I can't find AutoCorrect tools either/now, but it doesn't not seem to be doing the auto "scripting ordinals" thing, so I must have turned if off somehow, long ago. Anyway, for now, all of this leaves me with a dilemma: clearly the diagrams I am doing belong in Designer not Publisher, and I still have no way (in Designer) to overcome the combination of issues in my original post. I suppose I could work on the figures in Publisher now, and switch back to using Designer when these issues get sorted out, but I'm afraid that will create different issues for me later. P.S. I did try turning off AutoCorrect in Publisher (v2) and then switching to Designer (v2), hoping the preference setting would act globally somehow, but that didn't work either. P.P.S. Nobody has addressed my original #1. Could there really be no way to control the severity of the built in sub and superscript mechanism?
  24. Hello, I recently purchased the Affinity Apps for Windows. I am looking to convert a 30 page catalog from InDesign to Affinity Designer. I am looking tp convert a 30 page catalog from InDesign CS4 to Affinity Designer. I would like to put placeholders in all the product locations and use something like a csv or excel file to populate the product locations. Each location has several components; a background image, a product image, a description, a photo credit (which can be in any one of 3 positions, and a a image tag (special, new, best seller, etc) which can be in two locations. All the components would need their own style (which could be specified in the placeholders). Does Designer have any of this data merge capability? (or a scripting capability) Thanks Mark
  25. No. Affinity Publisher has a data merge feature but none of the apps has scripting capability (yet).
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.