2015-09-29, 01:49
You're very welcome. It's a good job I like a challenge (for the record, it took about five hours - I wanted to give up after 3 but I'm a stubborn old bugger ). And actually, it's one of those weird situations where if it hadn't been a challenge, I wouldn't have done it. I'm in the middle of re-writing the documentation, and was curious if there was anything I could learn from a quick attempt to switch Mimic over. Once I got started, I was determined to finish!
Not possible with the repo version of the script. The git version has some changes to custom properties where you can at least remove the 'None' option.
There's no option (though there is a feature request open for it) to set a default to all menu items, but a little bit of skilled skinning (IsEmpty(widgetIcon) | StringCompare(widgetIcon,...) should let you approximate that behaviour.
Not possible with the repo version of the script. The git version has some changes to custom properties where you can at least remove the 'None' option.
Code:
<propertySettings property="[Property]" buttonID="[buttonID]" title="[Dialog title]" showNone="[True/False]" imageBrowse="[True/False]" />
[Property] - The property of the shortcut that will be set
[buttonID] - [Optional] The ID of the button that will be used to set this property. If ommitted, you must use the window property 'chooseProperty' and send a click to 404
[Dialog title] - [Optional] The title of the dialog that will be shown to the user
[True/False] - [Optional] A boolean indicating whether a None option will be shown, and whether the user will be able to browse for an image or folder of images
There's no option (though there is a feature request open for it) to set a default to all menu items, but a little bit of skilled skinning (IsEmpty(widgetIcon) | StringCompare(widgetIcon,...) should let you approximate that behaviour.