Ignore that. I was mis-reading your code and thinking it was defined within a handler.
FWIW, if you had Console running with your eariler version, you would have seen entries like this:
-[NSTextField setStringValue]: unrecognized selector sent to instance 0x7f88c0bc6af0
That tells you there’s something wrong with the method you’re using.
Great.
I did have console running and saw the message. I’d used it’s output to debug the 1st part. But I didn’t know what to make out of that message in terms of knowing how to fix my code.
Thanks for the tip re: console,
My dialog is huge and complicated now, and overwhelmingly working really well.
This is non-essential, it would be possible for me to compile an extensive list of what people might want to type in this situation, and use a pop-up instead of a text field.
But it would be nice if I could use the text-field…
At the bottom of my dialog I’ve got a non-editable, script-updated text field showing information on what’s going to happen when the user clicks “OK” based on what they’ve input.
It’s all working great except with one user-modifiable text-field. I can only get it to update the information at the bottom to include the contents of the text field iff the user changes a popup after changing the text field. This will be confusing to the user, that the information shown at the bottom will not reflect the text they’ve input unless they change [any unrelated UI element in the dialog] after filling in the text field.
Here’s a simplified script showing the problem:
(the real script just has way too many dependencies to post / modify)
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit" version "2.0"
property fileNameField : {}
set {aPopup, theTop} to create popup {"1st Item", "2nd Item"} left inset 0 bottom 0 popup width 200
set {thePathLabel, theTop} to create label "Modified Text" left inset 0 bottom (theTop + 10) max width 400 aligns left without multiline
set {fileNameField, fileNameLabel, theTop, fieldLeft} to create side labeled field "" placeholder text "Enter Text Here" left inset 0 bottom (theTop + 10) total width 400 label text "OPTIONAL - Edit Print Area Name:" field left 0
fileNameField's setTarget:me
fileNameField's setAction:"changePathText:"
aPopup's setTarget:me
aPopup's setAction:"changePathText:"
set {buttonName, suppressedState, controlsResults} to display enhanced alert "Test" message "" as informational alert buttons {"Cancel", "OK"} giving up after 120 acc view width 600 acc view height (theTop + 10) acc view controls {fileNameField, thePathLabel, aPopup} without suppression
on changePathText:sender
set fileNameAddendum to fileNameField's stringValue()
my (thePathLabel's setStringValue:fileNameAddendum)
end changePathText:
Inputting text into the text field does not change the value shown in the “thePathLabel” field. However, changing the popup after modifying the text field does change “thePathLabel.” So it’s reading and writing the values OK, it just appears that the lines:
fileNameField's setTarget:me
fileNameField's setAction:"changePathText:"
Aren’t sufficient to detect a change to the text field and trigger the handler.
I was looking at this:
http://stackoverflow.com/questions/7010547/uitextfield-text-change-event
and this:
http://stackoverflow.com/questions/17385614/how-can-i-send-a-uicontroleventvaluechanged-event-from-my-custom-control
But was unable to figure out how to incorporate them into Applescript. Any help?
While I’m here:
When using my script, Console frequently logs:
Should I be worried about this / is there a way to fix it?
Also, I’m not quite done with the dialog yet, but so far in testing it works fine when run from Script Debugger or Script Editor, but if I put it on a FastScripts key command then FastScripts just crashes. I haven’t done anything to investigate that myself yet, and if I can’t solve it, I can address it in a separate post (or ask Daniel), but thought I’d throw it out here in case there’s some easy thing “everybody knows” like “when running ASObjC from FastScripts, you have to do [x] to keep it from crashing.”
Thanks,
Tom.
Actually, it’s updated when the user leaves the text field – the action is called when the user finishes editing.
To have it update each time the text changes, you can use a text field delegate method. So replace this:
fileNameField's setTarget:me
fileNameField's setAction:"changePathText:"
with this:
fileNameField's setDelegate:me
And then add this handler:
on controlTextDidChange:notif
set fileNameAddendum to fileNameField's stringValue()
my (thePathLabel's setStringValue:fileNameAddendum)
end controlTextDidChange:
Anything that refers to UI-prefixed classes instead of NS-prefixed classes is for iOS, not macOS. There are similarities, but also big differences.
This should only happen when you’re testing. Strictly speaking I’m playing a bit loose with threading, but it shouldn’t matter. The solution makes things a lot more complicated.
That shouldn’t happen. Please email me the actual script and crash info.
Thanks once again.
The text-updating is working brilliantly now. I rewrote a lot of what I had now that I’ve wrapped my head around Dialog Toolkit and the ASObjC components better.
Anybody:
On the script, it keeps getting much better, but I keep coming up with some additional case I have trouble solving.
This example shows it working great:
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit" version "2.0"
property ordersNmethods : {}
set ordersNmethods to {theOrders:{"Please Make a Selection", "Order Number 1, Production Method 2", "Order Number 2, Production Method 5"}, theMethods:{missing value, 2, 5}}
set {methodPopup, methodPopupLabel, theTop, matrixLeft} to create labeled popup {"1 - Some Method", "2 - Another Method", "3 - Still More Methods", "4 - The Rhythm Method", "5 - Methodical"} left inset 0 bottom 0 popup width 200 max width 400 label text "Override Method" popup left 0
set {orderPopup, orderPopupLabel, theTop, matrixLeft} to create labeled popup (theOrders of ordersNmethods) left inset 0 bottom (theTop + 20) popup width 200 max width 400 label text "Choose an Order" popup left 0
orderPopup's setTarget:me
orderPopup's setAction:"setMethod:"
set {buttonName, suppressedState, controlsResults} to display enhanced alert "Test" message "" as informational alert buttons {"Cancel", "OK"} giving up after 120 acc view width 700 acc view height (theTop + 10) acc view controls {methodPopup, orderPopup} without suppression
on setMethod:sender
set selectedOrderIndex to (my orderPopup's indexOfSelectedItem() as integer) + 1
set orderMethod to item selectedOrderIndex of theMethods of ordersNmethods
my (methodPopup's selectItemAtIndex:(orderMethod - 1))
end setMethod:
So in the dialog, the user needs to select which order they’re working on. They occasionally need to override the default “production method” set in the system. I need the default production method field to populate with the default, and it’s easy to do that when the user makes a selection for which order they’re working on. So that’s great.
The problem is that sometimes there’s only one option for what order they could conceivably be working on. That happens a lot. In that case, I don’t want the options on the top popup to start with “Please Make a Selection” like they do above, I just want that popup to be pre-selected with the only option so they don’t have to waste time making a selection off a list with one option.
But I still need the production method field to update to the method of the single option showing in the first popup.
So when the data looks like this:
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit" version "2.0"
property ordersNmethods : {}
set ordersNmethods to {theOrders:{"Order Number 1, Production Method 2"}, theMethods:{2}}
set {methodPopup, methodPopupLabel, theTop, matrixLeft} to create labeled popup {"1 - Some Method", "2 - Another Method", "3 - Still More Methods", "4 - The Rhythm Method", "5 - Methodical"} left inset 0 bottom 0 popup width 200 max width 400 label text "Override Method" popup left 0
set {orderPopup, orderPopupLabel, theTop, matrixLeft} to create labeled popup (theOrders of ordersNmethods) left inset 0 bottom (theTop + 20) popup width 200 max width 400 label text "Choose an Order" popup left 0
orderPopup's setTarget:me
orderPopup's setAction:"setMethod:"
set {buttonName, suppressedState, controlsResults} to display enhanced alert "Test" message "" as informational alert buttons {"Cancel", "OK"} giving up after 120 acc view width 700 acc view height (theTop + 10) acc view controls {methodPopup, orderPopup} without suppression
on setMethod:sender
set selectedOrderIndex to (my orderPopup's indexOfSelectedItem() as integer) + 1
set orderMethod to item selectedOrderIndex of theMethods of ordersNmethods
my (methodPopup's selectItemAtIndex:(orderMethod - 1))
end setMethod:
I need the second popop (“Override Method”) to come up with the method of the single, default order already selected.
The only way I could figure out how to do this is: when there’s only a single order choice, then reorder the Production Method list so the correct choice is at the top of the list.
But this isn’t a good option, because the users are used to these appearing in a certain order everywhere, and people are going to make incorrect selections when they’re out-of-order.
I’m concerned that this possibility is excluded with Dialog Toolkit because it looks to me like a “selectItemAtIndex:” or “selectItemWithTitle:” would need to be called at the time of Dialog Toolkit’s “display enhanced alert” call - Dialog Toolkit would need to accept a “default option” argument as a parameter of “create labeled popup.” Applescript, of course, comes to a stop from when it calls “display enhanced alert” until the dialog is dismissed, unless an option is chosen in the dialog to trigger a handler.
I can possibly do something clunky like, before calling “display enhanced alert” call a “selectItemAtIndex:” inside a delay with an “ignoring application responses,” but that sounds like it’s asking for trouble. Especially since my real dialog retrieves information off the web to populate the dialog, introducing a large variation in the time for the dialog to load.
Any ideas?
Shane: I PM’d you a link to download the whole thing to take a look at the FastScripts issue.
I’ve had three modes of failure there:
At first, it was just crashing - nothing would happen, and if I clicked on the Fastscripts widget in the menu bar the menu would’t come down, no Fastscripts scripts would run, and I’d have to force quit and relaunch it to get it to do anything.
Then it switched to opening a “Scripting Error” window that just says "Error Number: -1
Unknown error."
And at least once, it gave me an error that said something like [“Unable to use” or “Unable to load”] “framework “Foundation”” That’s the only remotely helpful error I’ve received, although it still seems like an odd error to me.
It sounds like you need to make a custom version of Dialog Toolkit that allows you to set the selected popup item.
It’s behaving for me. One thing to keep in mind with FastScripts:
Well that’s fascinating.
I had restarted FastScripts plenty of times. I still get the crashes.
So… either it was a system difference, or it was the one change I made to send the script to you - I commented out that handler that gets information on the open orders from our in-house CRM/ERP system in Chrome, and just made the function return dummy values.
So… it’s that function. Fastscripts runs the version I sent you just fine. It crashes when I un-comment out that dialog and have it get the info from Chrome.
So clearly, it’s not related to Dialog Toolkit.
Since it runs fine from Script Debugger and Script Editor, I’ll bring it up with Daniel.
Is editing Dialog Toolkit to accept this as straight-forward as I’m thinking? Add a “default selection” term to the handler, and feed it to a “selectItemAtIndex:” argument?
If it’s OK with you for me to dig into Dialog Toolkit and use a modified version, I’d be happy to give that a shot.
Thanks again,
Of course! Probably the safest way is to add a whole new handler, thus keeping compatibility with any existing stuff. And if it’s only for your use, you can make it a normal handler without terminology.
FYI, Shane is on vacation, if anyone else wants to look this over.
Right off the bat my new handler seemed to be doing great. I went ahead and modified the dictionary to add terminology for it. (I’ll show the original and my modified versions in each post here for comparison):
Then I saved the dictionary and added the handler:
on create popup entryList left inset theLeft bottom theBottom popup width theWidth
set thePopup to current application's NSPopUpButton's alloc()'s initWithFrame:(current application's NSMakeRect(theLeft, theBottom, theWidth, 26)) pullsDown:false
thePopup's addItemsWithTitles:entryList
return {thePopup, theBottom + 26}
end create popup
on create popup with default entryList left inset theLeft bottom theBottom popup width theWidth default selection defaultSelection
set thePopup to current application's NSPopUpButton's alloc()'s initWithFrame:(current application's NSMakeRect(theLeft, theBottom, theWidth, 26)) pullsDown:false
thePopup's addItemsWithTitles:entryList
thePopup's selectItemAtIndex:defaultSelection
return {thePopup, theBottom + 26}
end create popup with default
Gave it a try:
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit ROT"
set designsForDisplay to {"1-option", "2-option", "3-option"}
set {_printAreaPopop, theTop} to create popup with default designsForDisplay left inset 0 bottom 0 popup width 300 default selection 2
display enhanced alert "Select Your Print Area" message "" as informational alert buttons {"Cancel", "OK"} giving up after 120 acc view width 700 acc view height theTop acc view controls {_printAreaPopop} without suppression
And success! Works perfectly.
So then I made a modified version of “create labeled popup” to add the default:
Added the handler:
on create labeled popup entryList left inset theLeft bottom theBottom popup width popupWidth max width theWidth label text theLabel popup left popupLeft
if popupLeft ≤ theLeft then
set {theLabel, theTop, newWidth} to create label theLabel left inset theLeft bottom (theBottom + 6) max width theWidth aligns "left" without multiline
set popupLeft to (newWidth + 6)
set {thePopup, theTop} to create popup entryList left inset popupLeft bottom theBottom popup width popupWidth
else
set {theLabel, theTop, newWidth} to create label theLabel left inset theLeft bottom (theBottom + 6) max width (popupLeft - theLeft - 6) aligns "right" without multiline
set {thePopup, theTop} to create popup entryList left inset popupLeft bottom theBottom popup width popupWidth
end if
return {thePopup, theLabel, theTop, popupLeft}
end create labeled popup
on create labeled popup with default entryList left inset theLeft bottom theBottom popup width popupWidth max width theWidth label text theLabel popup left popupLeft default selection defaultSelection
if popupLeft ≤ theLeft then
set {theLabel, theTop, newWidth} to create label theLabel left inset theLeft bottom (theBottom + 6) max width theWidth aligns "left" without multiline
set popupLeft to (newWidth + 6)
set {thePopup, theTop} to create popup with default entryList left inset popupLeft bottom theBottom popup width popupWidth default selection defaultSelection
else
set {theLabel, theTop, newWidth} to create label theLabel left inset theLeft bottom (theBottom + 6) max width (popupLeft - theLeft - 6) aligns "right" without multiline
set {thePopup, theTop} to create popup with default entryList left inset popupLeft bottom theBottom popup width popupWidth default selection defaultSelection
end if
return {thePopup, theLabel, theTop, popupLeft}
end create labeled popup with default
Call it:
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit ROT"
set designsForDisplay to {"1-option", "2-option", "3-option"}
set {_printAreaPopop, printMethodLabel, theTop} to create labeled popup with default designsForDisplay left inset 0 bottom 0 popup width 200 max width 400 label text "OPTIONAL - Override Production Method:" popup left 0 default selection 2
display enhanced alert "Select Your Print Area" message "" as informational alert buttons {"Cancel", "OK"} giving up after 120 acc view width 700 acc view height theTop acc view controls {_printAreaPopop} without suppression
and… nothing.
I’ve been over it and over it and just can’t find my error… I just don’t see why calling “create popup with default” works when called directly, but “create labelled popup with default” doesn’t work to set the default.
I’ve had Console open, but it doesn’t log anything.
Any help?
If you want to download my modified version of Dialog Toolkit for testing so you don’t have to paste in all my edits, I put it here:
https://www.dropbox.com/s/67mnhmlm9scyzuy/Dialog%20Toolkit%20ROT.scptd.zip?dl=0
Since the first function works, I feel like I must have some very stupid mistake.
Thanks in advance,
Shane messaged me to try putting the call to the handler straight into the library, and run it from Script Editor while holding down Control. I did that - and it worked - the correct choice was selected.
So I tried if from Script Editor as a separate script - and it worked. So I went back to Script debugger - and now it works there as well.
So it didn’t work because ??? I haven’t changed anything.
But now it’s working, so at least that’s the good news. Probably something just needed to be restarted to make it work, and now it’s a new day, so whatever it was is restarted now. I wasn’t running the script from Fastscripts, but from Script Debugger, which I didn’t think cached libraries. But whatever it was, now everything’s working without actually changing anything.
Thanks again for all the help, Shane.
Tom,
You’re misunderstanding how library caching works. Libraries are cached per component instance of AppleScript. So an app like FastScripts uses a single instance for all scripts, which means you need to relaunch it if you modify a library.
Script Debugger (and Script Editor) uses a separate instance for each document, and each time you compile, it creates a new instance. But if you modify a library and then re-run a calling script without recompiling, the document’s instance will still use the cached version.
Short version: when you modify a library, you should dirty and recompile any calling script to clear any caching.
Good news: the FastScripts crash was tracked down to a bug that had cropped up on that individual script related to Script Debugger. Simply copying and pasting the code into a new Script Debugger document fixed the issue.
I’d like to find a way to disable clicking “OK” and only allow clicking “Cancel” until an acceptable set of choices have been made in the dialog.
I was hoping with a reference to the button I could just put handlers that do
[reference to button] setEnabled:no
[reference to button] setEnabled:yes
or is it setState:true ?
But I can’t figure out how to reference the button.
Each UI element I make to go into the “display enhanced dialog” argument has a variable that’s a reference to it:
set {aPopop, printAreaPopupLabel, theTop, matrixLeft} to create labeled popup ...
so I can send commands to this feature by addressing “aPopop’s [whatever]”
But the buttons are created in the “display enhanced alert” argument, but no variable is set to represent the alert dialog itself.
Do I need to make a modified version of “display enhanced alert” that returns a fourth argument, “theAlert”?
So my Applescript would look like:
set {aPopop, printAreaPopupLabel, theTop, matrixLeft} to create labeled popup {"One", "Two", "Three"} left inset 0 bottom 0 popup width 300 max width 400 label text "Selection" popup left 0
aPopop's setTarget:me
aPopop's setAction:"setActive:"
set {buttonName, suppressedState, controlsResults, alertReference} to display enhanced alert "Title Text" message "" as informational alert buttons {"Cancel", "OK"} giving up after 120 acc view width 700 acc view height theTop acc view controls {aPopop} without suppression
on setActive:sender
-- my (alertReference's [reference button by name?] setState:false
end setActive:
Please let me know if I’m on the right track at all here,
Thanks,
Tom.
probably. Then use something like:
(theAlert's |buttons|()'s objectAtIndex:0)'s setEnabled:false
And you must do that on the main thread.
Thanks for helping out even when you’re on vacation!
Here’s what I’ve got:
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit ROT"
set {aPopop, printAreaPopupLabel, theTop, matrixLeft} to create labeled popup {"One", "Two", "Three"} left inset 0 bottom 0 popup width 300 max width 400 label text "Selection" popup left 0
aPopop's setTarget:me
aPopop's setAction:"setActive:"
set {buttonName, suppressedState, controlsResults, theAlert} to display enhanced alert with return reference "The Title" message "" as informational alert buttons {"Cancel", "OK"} giving up after 120 acc view width 700 acc view height theTop acc view controls {aPopop} without suppression
on setActive:sender
my ((theAlert's |buttons|()'s objectAtIndex:0)'s setEnabled:false)
end setActive:
And so far I’ve been running it on the main thread by running it from Script Editor with [control]. I figured I’d move it back to Script Debugger and figure out how to run it in the main thread there after I have it working.
Currently, it does not disable, and console logs:
I’m used to using UI Browser or Accessibility Inspector to browse UI’s for Applescript UI scripting, but don’t know how to figure out how to properly refer to UI elements in AS Obj C.
So… I was thinking about this some more, and am wondering if there isn’t a “catch 22” here…
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit ROT"
set {aPopop, printAreaPopupLabel, theTop, matrixLeft} to create labeled popup {"One", "Two", "Three"} left inset 0 bottom 0 popup width 300 max width 400 label text "Selection" popup left 0
aPopop's setTarget:me
aPopop's setAction:"setActive:"
set {buttonName, suppressedState, controlsResults, theAlert} to display enhanced alert with return reference "The Title" message "" as informational alert buttons {"Cancel", "OK"} giving up after 120 acc view width 700 acc view height theTop acc view controls {aPopop} without suppression
set someVariable to (theAlert's |buttons|()'s objectAtIndex:0)
return someVariable
on setActive:sender
my ((theAlert's |buttons|()'s objectAtIndex:0)'s setEnabled:false)
end setActive:
This still gets the same error, but here it returns
so that looks to me like it’s finding “(theAlert’s |buttons|()'s objectAtIndex:0)”
So I was thinking about my addition of returning a reference, and I’m thinking that this doesn’t actually work with order-of-operations here…
All the variables set when the “display enhanced alert with return reference” command is called aren’t going to be set until that handler in the dictionary completes and returns to executing the script, right? So “theAlert” isn’t defined in my script until the user has clicked “OK.” But the “setActive:” handler is being called and using the “theAlert” variable before that dialog is returned.
If that’s correct, then I’m thinking that, rather than simply modifying “display enhanced alert” to be “display enhanced alert with return reference” and return the “theAlert” variable the handler used, I need to construct an alternate version of “display enhanced alert” that first just returns what’s constructed as “theAlert,” then I need to call that separately.
I’ll take a look at doing that. I feel like this has to be the problem. I should have thought of this.
Hooray!
It seems I correctly identified the problem and solution.
New functions in library:
on return enhanced alert mainText message theExplanation as styleType buttons buttonsList suppression showSuppression acc view width theWidth acc view height theHeight acc view controls controlsList
if styleType = critical alert then
set styleNum to 2
else if styleType = warning alert then
set styleNum to 0
else
set styleNum to 1
end if
set theError to current application's AEInteractWithUser(-1, missing value, missing value) -- -1 is kAEDefaultTimeout
if theError is not 0 then
error "User interaction disallowed" number theError
end if
-- make the accessory view
set theAccessoryView to current application's NSView's alloc()'s initWithFrame:(current application's NSMakeRect(0, 0, theWidth, theHeight))
theAccessoryView's setSubviews:controlsList
-- reverse buttons because they get added in reverse order cf AS
set buttonsList to reverse of buttonsList
-- create an alert
set theAlert to current application's NSAlert's alloc()'s init()
-- set up alert
tell theAlert
its setAlertStyle:styleNum
its setMessageText:mainText
its setInformativeText:theExplanation
repeat with anEntry in buttonsList
(its addButtonWithTitle:anEntry)
end repeat
its setShowsSuppressionButton:showSuppression
its setAccessoryView:theAccessoryView
its (|window|()'s setAutorecalculatesKeyViewLoop:true)
end tell
set alertRecord to {theAlert:theAlert, controlsList:controlsList, buttonsList:buttonsList}
return {alertRecord}
end return enhanced alert
on show returned alert alert reference alertRecord giving up after giveUp
set theAlert to theAlert of alertRecord
set controlsList to controlsList of alertRecord
set buttonsList to buttonsList of alertRecord
-- if giveUp value > 0, tell the app to abort any modal event loop after that time, and thus close the panel
if giveUp > 0 then current application's NSApp's performSelector:"abortModal" withObject:(missing value) afterDelay:giveUp inModes:{current application's NSModalPanelRunLoopMode}
-- show alert in modal loop on main thread
my performSelectorOnMainThread:"showTheAlert:" withObject:theAlert waitUntilDone:true
-- if a giveUp time was specified and the alert didn't timeout, cancel the pending abort request
if giveUp > 0 and returnCode is not current application's NSModalResponseAbort then current application's NSObject's cancelPreviousPerformRequestsWithTarget:(current application's NSApp) selector:"abortModal" object:(missing value)
-- get values after alert is closed
set suppressedState to theAlert's suppressionButton()'s state() as boolean
set buttonNumber to returnCode mod 1000 + 1 -- where 1 = right-most button
if buttonNumber = 0 then
set buttonName to "Gave Up"
else
set buttonName to item buttonNumber of buttonsList
end if
-- get values from controls
set controlResults to {}
repeat with aControl in controlsList
if (aControl's isKindOfClass:(current application's NSTextField)) as boolean then
set end of controlResults to aControl's stringValue() as text
else if (aControl's isKindOfClass:(current application's NSPopUpButton)) as boolean then
set end of controlResults to aControl's titleOfSelectedItem() as text
else if (aControl's isKindOfClass:(current application's NSButton)) as boolean then
set end of controlResults to aControl's state() as boolean
else if (aControl's isKindOfClass:(current application's NSPathControl)) as boolean then
set end of controlResults to aControl's |URL|()'s |path|() as text
else if (aControl's isKindOfClass:(current application's NSMatrix)) as boolean then
set end of controlResults to aControl's selectedCell()'s title() as text
else -- NSBox
set end of controlResults to missing value
end if
end repeat
return {buttonName, suppressedState, controlResults}
end show returned alert
new test script:
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit ROT"
property alertRecord : {}
set {aPopop, printAreaPopupLabel, theTop, matrixLeft} to create labeled popup {"One", "Two", "Three"} left inset 0 bottom 0 popup width 300 max width 400 label text "Selection" popup left 0
aPopop's setTarget:me
aPopop's setAction:"setActive:"
set {alertRecord} to return enhanced alert "The Title" message "" as informational alert buttons {"Cancel", "OK"} acc view width 700 acc view height theTop acc view controls {aPopop} without suppression
set {buttonName, suppressedState, controlsResults} to show returned alert alert reference alertRecord giving up after 120
on setActive:sender
set theAlert to theAlert of alertRecord
((theAlert's |buttons|()'s objectAtIndex:0)'s setEnabled:false)
end setActive:
And it works!
However, I’ve been trying to get the syntax right for running it on the main thread in Script Debugger, and that’s been an issue for me so far.
Oops! Nope, just thought of something else and tried that, and now I’ve got it working from Script Debugger like this:
use AppleScript version "2.4" -- Yosemite (10.10) or later
use framework "Foundation"
use scripting additions
use script "Dialog Toolkit ROT"
property alertRecord : {}
set {aPopop, printAreaPopupLabel, theTop, matrixLeft} to create labeled popup {"One", "Two", "Three"} left inset 0 bottom 0 popup width 300 max width 400 label text "Selection" popup left 0
aPopop's setTarget:me
aPopop's setAction:"setActive:"
set {alertRecord} to return enhanced alert "The Title" message "" as informational alert buttons {"Cancel", "OK"} acc view width 700 acc view height theTop acc view controls {aPopop} without suppression
set {buttonName, suppressedState, controlsResults} to show returned alert alert reference alertRecord giving up after 120
on setActive:sender
my performSelectorOnMainThread:"setActiveOnMain:" withObject:{missing value} waitUntilDone:true
end setActive:
on setActiveOnMain:sender
set theAlert to theAlert of alertRecord
((theAlert's |buttons|()'s objectAtIndex:0)'s setEnabled:false)
end setActiveOnMain:
At first I was trying to get the syntax right to call the “setActive:” handler from “aPopop’s setAction:” AND run it on the main thread as one call. Maybe that’s possible, but I couldn’t get it. Then it occurred to me to just nest the functions.
So thanks so much!
Feel free to tell me to take a hike if I’m driving you nuts here, but there’s always something else that would make the UI better. I’d love to have a super obvious indicator when the UI was able to fully populate itself with default values, so the user should be able to just hit “return” unless they know they’re doing something unusual and will have to modify the defaults. I was hoping to maybe set the entire background of the dialog to a pale green when everything’s auto-filled, and a pale red when they have to pay attention. Or maybe change the icon to signify these things. What I’ve been able to Google up so far does not sound promising on the background color.
I can, of course, change a label, or even the dialog title, but I’ve found UI-wise that anything requiring someone to read text is much slower for users than something like the background color being as an indicator.
*** EDIT AT END - Figured it out ***
Now I’m having the same issue I had with having a default selection on popup lists, but with deactivation of the “OK” button.
It’s working fine to activate or deactivate the “OK” button based on any user interaction, but the intention was, until the a valid set of selections have been made, for the button to be deactivated.
This means that it must be deactivated when the dialog opens, and I’ll use logic to activate it. The activation part looks good, but I can’t get it to be deactivated on open.
I’ve been trying to modify Dialog Toolkit for this, but it seems to be back to the “chicken and the egg” problem that
does not work until the Alert window is open.
Adding:
inside Dialog Toolkit when the dialog was being constructed did work, but doing the same inside dialog toolkit for setting button activation does not, it can only be deactivated/activated once the dialog is shown.
Putting it inside the “showTheAlert” handler in Dialog Toolkit immediately after
doesn’t invoke it until the dialog has been dismissed.
I’ve been looking through the documentation for something like “defaultEnabled” under NSAlert and NSButton, but with no luck.
Man, I keep writing these and then figuring out something else to try when I’m basically done… then I think about just not posting, but I figure it’s better to post the problem/solution in the thread in case anyone in the future Google’s it up.
Functioning edit to Display Enhanced Alert making the buttons:
repeat with anEntry in buttonsList
set aButton to (its addButtonWithTitle:anEntry)
if buttonActive is false then
if anEntry as text is "OK" then
(aButton's setEnabled:false)
end if
end if
end repeat
I’m having trouble with setting the icon.
I modified “Display Enhanced Alert” in the following way:
tell theAlert
its setAlertStyle:styleNum
its setMessageText:mainText
its setInformativeText:theExplanation
repeat with anEntry in buttonsList
set aButton to (its addButtonWithTitle:anEntry)
if buttonActive is false then
if anEntry as text is "OK" then
(aButton's setEnabled:false)
end if
end if
end repeat
its setShowsSuppressionButton:showSuppression
its setAccessoryView:theAccessoryView
its (|window|()'s setAutorecalculatesKeyViewLoop:true)
its icon:theImage -- <- ADDED THIS
end tell
It appeared to me that that was the right syntax from the Xcode documentation…
And the documentation for “icon” says it wants an NSImage as it’s argument.
I pass theIcon into “Display Enhanced Alert” as an argument.
In the calling script, I added “use framework “AppKit”” at the top, and then I set the variable passed as “theIcon” as follows:
set dialogIconPath to "/Volumes/Hackintosh HD/Users/work/Dropbox/Clipart Project/ROT Setup/Script Dependencies/AIC_ICON.png"
set dialogIcon to current application's NSImage's alloc()'s initWithContentsOfFile:dialogIconPath
And I pass “dialogIcon” to “Display Enhanced Alert” where it becomes “theIcon” variable.
The error I get is:
Any help?
Thanks,
Tom.
Try:
its setIcon:theImage
Ah, thanks, that seems obvious in retrospect, especially looking at how you set all the other values.
Hard to get used to gluing words together and changing capitalization to build commands when I’m used to Applescript.