View Single Post
Old 02-16-2008, 08:02 AM   #159
Enforcer
Confusion Master
Enforcer's CarPC Specs
 
Enforcer's Avatar
 
Join Date: Sep 2003
Location: If you go down to the woods today, You're sure of
Vehicle: 1997 BMW E36 328I
Posts: 9,965
My Photos: ()
Quote: Originally Posted by treetop777 View Post
Kind-a begs for those numbers to be bigger. IMO

Quote: Originally Posted by blk02si View Post
The buttons for the #'s are much larger than the # itself.

I have taken the NUMOSK graphic and and used that to keep it standard with the rest of the skin, as blk02si says the buttons extend to the lines and meet halfway between each other.


Quote: Originally Posted by blk02si View Post
Looks really good Enforcer! I am very interested in the Upd8 menu.




Quote: Originally Posted by blk02si View Post
Just so you know the floating menu is all AUtoIT. The script sends commands directly to iGuidance, it does not use RR to send the commands at all. AUtoIT is quite clever in how it can pass commands to other windows applications, so the only thing RR needs to handle is the embedding. As long as the traffic CAM app has a window title and some way of passing key strokes, mouse clicks, shortcuts, etc. to it the floating menu would work as is does in the CWiG script.

Well for it to work with traffic cams it would also need to be able to receive commands to tell it to change graphic when TC switches screen.


Here's the two screens

The first is the main camera screen (of which there are three, but the buttons on the left stay the same) then second is the search screen which has different buttons and therefore button codes, these are screens within my program not RoadRunner screens, so the floating menu would have to notified that which screen my program is in and then charge appropriately.




Last edited by Enforcer; 02-16-2008 at 08:15 AM.
Enforcer is offline   Reply With Quote