ctwise
-
Content Count
307 -
Joined
-
Last visited
-
Days Won
23
-
Beery reacted to a post in a topic:
Funnel (a variant of the Pipe workflow)
-
dakush reacted to a post in a topic:
Funnel (a variant of the Pipe workflow)
-
Calfy reacted to a post in a topic:
Microsoft Remote Desktop
-
khangazun reacted to a post in a topic:
VPN applescript is busted in El Capitan
-
VPN applescript is busted in El Capitan
ctwise replied to ctwise's topic in Workflow Help & Questions
This probably won't work either then, but you can give it a try: property newLine : (ASCII character 10) set results to "" set flag to true tell application "System Events" tell network preferences to set locs to every location repeat with loc in locs tell loc set vpns to every service repeat with vpn in vpns if flag is true then set flag to false else set results to results & newLine end if set vpnName to (the name of vpn) as string set results to results & vpnName set results to results & "|" & (kind of vpn) end repeat end te -
Vote for this - https://remotedesktop.uservoice.com/forums/287834-remote-desktop-for-mac/suggestions/9280833-allow-the-application-to-be-controlled-with-apples The workflow breaks constantly due to having to script the GUI - Microsoft keeps making GUI changes and throwing up dialog boxes. Until Microsoft makes the app scriptable the workflow will remain buggy.
-
VPN applescript is busted in El Capitan
ctwise replied to ctwise's topic in Workflow Help & Questions
Yeah, since the AppleScript is busted, you have to use the command-line. You can get the connection status of a VPN using this command-line: scutil --nc show "<vpn name>" | grep Disconnected > /dev/null That returns an exit code of zero if the VPN is disconnected, anything else and the VPN is connected. You can start a VPN with this command-line: scutil --nc start "<vpn name>" And stop it with this command-line: scutil --nc stop "<vpn name>" So a Ruby script to toggle the status of a VPN connection would be: vpn_name = ARGV[0] status = system("scutil --n -
Thanks to _patrick, I have updated my VPN workflow to work correctly on El Capitan. If you've upgrade to El Capitan and your VPN workflow no longer works - try this one - http://www.packal.org/workflow/vpn-toggle
-
Looking for info from anyone on this issue. Pulling VPN info using AppleScript appears to be broken in El Capitan. Most services have an empty (null) value for the current configuration. So you can't determine connection status.
-
This might help - http://www.packal.org/workflow/menu-bar-search
-
I just updated the workflow on Packal to add remote triggers.
-
I suggest using the new queue setting to terminate the script filter when a new keypress is received. It shaves a few microseconds off when typing, not a big difference but definitely adds a snappier feel.
-
Very, very, very few workflows will benefit from compilation. Most workflows actually _do_ very little work. If a script takes 100 milliseconds and a compiled version takes 10 milliseconds, you won't be able to tell the difference. The exception is when your workflow takes seconds to run _and_ the reason for the delay is computation, not network lag. A much more likely reason for compiling code for a workflow is that it's the only (or easiest) way to interact with something in OS/X.
-
Yep, it's well and truly broken. There's no longer a search so there's no way to narrow down the items and select one programatically. Crap. On the other hand, it looks like 8.0.6 has full URI support now. It's possible I can generate the RDP URIs and use those to connect. It won't be for a while though.
-
Yep, it's one of the downsides of UI scripting instead of true AppleScript support from the app. I put in a feature request on the Microsoft support site but I'm not holding my breath.
-
Awesome! I added it to the workflow.
-
You are correct. The only way in Alfred to act on selected text is through a hotkey. Otherwise the Alfred input box becomes the text source. I'll update the workflow.
-
It's the upgrade notice dialog box that comes up. Start the RDP app directly and dismiss the dialog box. Everything will go back to normal. You can thank: 1. Microsoft for displaying the stupid box. 2. Microsoft for not supporting Applescript in the app. 3. The brittleness of UI scripting since there's no Applescript support.
