Did you add it in a folder called Script Libraries?
No. That was it. Thx.
It’s a shame, though. Personally, I preferred the idea of the “flatten” feature. Simpler and quicker. It’d also be quicker to debug as you could see exactly what library code is being called. Doing it the “supported” way, you have to assume that the user hasn’t messed with the library script, but there’s no way to tell from the script they give you. Be nice if Mark could just slip that feature back in as an option at some point. :)
On 17 Jun 2016, at 21:08, Shane Stanley < email@hidden> wrote: And better to use:
use scripting additions use sortLib : script “sorted”
set resultsList to {"d", "a", "b"} tell sortLib to quickSort(resultsList)
It seems the “use” command isn’t necessary. This works:
use scripting additions set resultsList to {"d", "a", "b"} tell script "sorted" to quickSort(resultsList) —> {"a", "b", "d"}
For me, that’s more perspicuous, especially if I’m wading through a hundred lines of code (pet quibble: an option to have line numbers always on in Preferences would be nice; I already gave it a shortcut, but it’s a bit annoying to have touse it every time I open a script).
On 17 Jun 2016, at 19:39, Shane Stanley <email@hidden> wrote:
Type "use" and hit esc or F5 to bring up the code completion list. You'll see an option that begins "use libVariable:". Cursor
No, not seeing that, but never mind. I’ll figure that out another day. I’ve seen enough to justify the (new, improved!!) pricing.
Best
Phil
|