Delvy Thanks for the followup on that. my particular application of this is within a Filemaker Pro process - a script which runs this applescript in the background. The user never sees the actual

There is a way around that issue: stop the script from storing its properties and top-level variable values. That means doing something like changing its privileges, code-signing it, or even using a

Dave, you will not be able to see the command in your Terminal. do shell script does not use Terminal to send it commands, so it is sheltered from Terminal’s command history. However,

I was recommended to come here, by some knowledgeable folks on a Filemaker Pro forum. So, I'm using some older versions in an active filemaker solution (FMPA 13, 14, 15), and need to enhance some

That pretty much fits my definition :) But thank you. I'll see which of your approach and Yves is easier to fit in my code and will probably come back here for further hints. In the meanwhile, I

I guess it depends on your definition of weird. set fullPath to "/path/to/folder/path/from/folder/file" set rootPath to "/path/to/folder" set relpath to "." & text ((length of rootPath) + 1) thru -1

I seem to be wasting a lot of time on something that may already exist... I'm trying to find a way to add/subtract paths to files. Like, I have a path from / and I want to subtract it from the path

Actually, once a control has focus, tapping the space bar will action that control, and once you are used to this, it means you don’t have to move your hand from the keyboard to the mouse nearly as

The main thing it does is destroys the tabbing order. By default, tabbing takes you through the fields of a dialog in a left-to-right/top-to-bottom order, but in more complex dialogs developers often

Shane, Could you elaborate on the side-effects you are referred to? I haven’t noticed anything. Robert Poland iMac, Late 2013, 14,2 3.2 GHz Intel Core I5, 27” 16 GB Ram, 1TB Fusion HD OS X

Ok. Thank you! Jean-Christophe Helary ----------------------------------------------- @brandelune http://mac4translators.blogspot.com

Those I mentioned are just the built-in defaults. Custom shortcuts can be applied to any buttons -- just not using "display dialog" or "display alert". A simple example is my Dialog Toolkit Plus

Ok. I'm pretty sure I've seen them in other places too, but I'm fine with your answer. Return being the default button, right ? Jean-Christophe

I suspect you're thinking of "Don't Save". Alerts are hard-wired by default to map escape/command-. to Cancel, return to OK, and command-D to Don't Save: display alert "Test" buttons {"Cancel",

Maybe not all, but some buttons can be accessed by hitting Cmd+the first letter, or something like this. It used to be that a TextEdit dialog reacted to Cmd+D for Delete, but now it is "Change

"Normal" Mac dialogs don't show keyboard equivalents. -- Shane Stanley <sstanley@...> <www.macosxautomation.com/applescript/apps/>, <latenightsw.com>

Yes, but that's not what there is in normal Mac apps, or am I wrong? I'd like to have something that acts as normal Mac dialogs. Is that possible? Jean-Christophe

It will if you go to Preferences -> Keyboard -> Shortcuts and change Full Keyboard Access to All controls. But if you do so, you'll probably also find the side-effects more annoying than it's

Not in 10.13 on my machine. Tab won't change the focus. Jean-Christophe

This script works as I said with OS10.13.2. display dialog "See the pretty buttons!" buttons {"Cancel", "OK", "Some other button"} cancel button "Cancel" default button "OK" Robert Poland Fort