Thread: Send front end commands to ICE3

Hmmm....isn't there a way you can call the software buttons onscreen if you only know their name? I thought you could use gui scripting and there was an inspector tool you could run that would tell you the name of the object (button) on the screen.

Using applescript, you could issue a command to that button.

It might be better to wait for keyboard commands but that is one way to do it.

Originally Posted by Bugbyte

Hmmm....isn't there a way you can call the software buttons onscreen if you only know their name? I thought you could use gui scripting and there was an inspector tool you could run that would tell you the name of the object (button) on the screen.

Using applescript, you could issue a command to that button.

It might be better to wait for keyboard commands but that is one way to do it.

Remember the name of that inspector tool ??

If the creator would chime in...it would all comes together for good

Here is a nice tutorial on how to UI script. And here is where you can get the UI element inspector tool.

Also, you can probably poke around inside the ICE3 app using XCODE and the interface builder to determine the names of some of the buttons.

^^WOW thanks BugByte, as usual always have some great answers/solution for US. I'll work my way arround with this. It's really simple to use I may have to WRITE on this forum about this, it will simply revolutionate the MacCar frontEnd lol

FYI: I did poke inside ICE3 and I got all commands I needed in 2 minutes lol...this tool is simply AWESOME. Now I need to script this and assign some commands to those codes...and finally assign that command to my hackedup USB controller

This post made my day thanks again! will keep u guys updated!

OK! I was so Happy that I took some time to analyse this. I have some good knowledge into scripting and this is the most basic scriptin I did to this date (except GUI VB lol)

Here's how I did:

1) Get the command needed; AUDIO CoverFlow
- Use UI Element Inspector and point your mouse over the button
- Freeze the UI Element Inspector to copy and paste the description into a file
- Analyse the description
AUDIO (coverflow)

<AXApplication: “ICE³”>
<AXWindow: “”>
<AXGroup>
<AXButton: “Coverflow View”>

Attributes:
AXRole: “AXButton”
AXRoleDescription: “button”
AXHelp: “(null)”
AXEnabled: “1”
AXFocused (W): “0”
AXParent: “<AXGroup>”
AXWindow: “<AXWindow: “”>”
AXTopLevelUIElement: “<AXWindow: “”>”
AXPosition: “x=-3 y=478”
AXSize: “w=170 h=250”
AXTitle: “Coverflow View”

Actions:
AXPress - press

- Use the usefull information from that command to create a script...
- Open script EDITOR and type this

Code:

tell application "System Events"
	tell process "ICE³"
		click button "CoverFlow View" of group 1 of window 1
	end tell
end tell

I pasted all useufull info in BOLD so that you guys understand well where does the command come from...Coming from that, you just need to adjust the button and where the button is located. I'll create a simple file that will state all buttons script so that everybody could use this easily without having to use UI Element Inspector!!!

Hope this will help other people

THANKS AGAIN BugByte, ur a king!!

I always had problems figuring out the group 1 window 1 thing. How did you know that was what they were?

Also, I suppose I can use these scripts to trigger key sequences on my powermate? That would be pretty choice!

^^I simply looked at the code the button was giving me..
If you take a look at the exemple I posted

Code:

<AXApplication: “ICE³”>
<AXWindow: “”>
<AXGroup>
<AXButton: “Coverflow View”>

This is all You need or this is the most important part!!

If I show you the same code that way...

Code:

<AXApplication: “ICE³”>
<AXWindow: “”>   (Window 1)
         <AXGroup> (Group 1) 
<AXButton: “Coverflow View”>

Code:

click button "CoverFlow View" of group 1 of window 1

SYNTAX
click button is the action
CoverFlow View is the name of the AXButton
of window 1 - <AXWindow: “”>
of group 1 - <AXGroup>


I'm creating the database of all commands of the program and will post it soon.

For instance the HOME command isnt the same at every screen..

I saw

Code:

<AXWindow: “”>   (Window 1)
         <AXGroup> (Group 1) 
               <AXSheet> (Group 1)

In the end it's pretty simple. You save the script and it gets called buy whatever you wan't; a button or a USB Remote like the PowerMate that I always wanted to use but never find a good place so I can keep the car lookin OEM

I'll keep you guys updated