@cooldtp@indiscripts If you're referring to https://t.co/hDlKCfeK3d, that bug was fixed almost immediately, but of course not in the older versions (anything before InDesign 2023), since we don't update older versions with bug fixes. (Or else we'd be supporting them all indefinitely.)
[EN] Seems that @emsoftware's InData/InFlow plugin leads to a critical bug (InDesign crash) as soon as an external script (#ExtendScript) wants to access the properties of a Character objet:
var pp = https://t.co/tpC3mYCgoe; // CRASH
Sometimes it's not your code that's buggy!
@drawerinm@chrisdwells_ Sure thing! Let us know how your testing goes, for good or ill. Ideally, via email to [email protected], as Twitter/X threads are kinda clumsy. But, up to you.
@drawerinm@chrisdwells_ Yes, our website has been http:-only (now trumpeted as "not secure" by
the major browsers as they try to browbeat people into using https:
only, even for pure informational sites like ours) forever,If/when you go to order, you'll be entering a secure site, of course.
@agentbey Hi, David! Unfortunately, none of the Affinity products are extensible. Plus the base products are inexpensive enough that it'd be hard to sell plugins at a reasonable cost into that market.
@chrisdwells_ Here's a little secret: you can get the release candidates for WordsFlow from https://t.co/nK1zIGtPsw . We should the website updates today sometime.
@chrisdwells_ No, the complexity is mostly internal -- we made some serious internal engineering investments which we've been pushing on for some months and it's all just coming together.