Hopfully V3 will have more "universal" nudge settings. I've done a lot of work to try to make the INI files compleatly universal from front-end to front-end as well as from PC to PC.
Yeh, its always been like this.... the different frontends seem to use different embedding proceduresOriginally Posted by d_sellers1
![]()
We'll PM them when necessaryOriginally Posted by camsgs3
![]()
Hopfully V3 will have more "universal" nudge settings. I've done a lot of work to try to make the INI files compleatly universal from front-end to front-end as well as from PC to PC.
RPM, I followed a CF thread here because I just began trying to use iG with CF. I've got a hefty bit of experience with graphic design and I'd be more than happy to skin for this, but first I think I should become more acquainted with SB and how the skins work. I'll do some studying tonight. Heh.Originally Posted by RPM_VR4
Ride: 2004 Nissan Murano SL AWD/Sheer Silver/Black Leather/factory HIDs.
MoPuter: Transflectivized Lilli 7", EPIA M-10000, 512Mb RAM, 160Gb WD, SBLive!, 54g WLAN, Holux GM-213, 160W M2-ATX PSU
I'm working with Net Stumbler, and I'm finding very difficult to skin an app like NS where the window name changes as you use it.
For example: If I have a file called myfile opened, the window name would be "Network Stumbler - [myfile]", but if I close this file, then the window name would be "Network Stumbler" and SB will lose the embedding...
0l33l suggested that we try the window class name. How do I find it?
Also, is there is a command that I can put in a button to close SB ??
Ikea Case. Epia M10000.M1-ATX. 512 Mb. 2,5" 80 GB HDD. 7" Lilliput. BU-303 GPS. Sony Joystick.
Status --> Lilliput Installed (not indash yet..)
BraveCar 2.5
You should use the AutoIt Window Tool to find the class name, but that won't work until V3 is released (1-week or less). I do not know how to find partial matches, however, V3 will not "un-embed" if the window name changes like V2.5 does.Originally Posted by Bravellir
Not yet. I will add that to the ToDo list for V3.Originally Posted by Bravellir
Actually, the way the skins work is changing greatly for V3. Maybe you can help me with that. Currently I'm thinking there will be a single transparent image over the entire window. When a "button" is clicked, a "button-down" image (which is just the size of the button) will be displayed over the main "all-buttons-up" image and the definition for the positioning of that "down-image" will also define the "click mapping" for the main image.Originally Posted by Thann
When a button is pressed (in addition to displaing the "down-image") it will run a script composed of these commands:
For example, the Enter button will:Code:Run(Program) Will run a program or a file associated with a program (including AutoIt scripts). RunWait(Program) Will run a program and wait for it to exit. LoadSkin(Section) Will change the "single transparent image" and setup new buttons according to a [Section]. Embed(Section) Will embed a new window accordint to a [Section]. Send(Keys) Will send key presses to whichever window was last embedded. Click(x,y) Will click whichever window was last embedded at its X/Y OnTop(True/False) Will make SKINbedder always-on-top (to hide new iG windows until embedded) DoubleClick(x,y) RightClick(x,y) Wait(milliseconds) Exit(Program) I just added this one ;) It will be able to close any program including SKINbedder. Probably many more commands eventually.
OnTop(True),Send(Enter),Send(Enter),Send(Enter),Se nd(Enter),Embed(iGEnter),LoadSkin(EnterOSK),OnTop( False)
Originally Posted by RPM_VR4
I think I created every button for all the functions in IG. Both the transparent, and the brushed metal.
While you may not want to use them, you are more then welcome to use them.
Michael
...I love the French language...especially to curse with...Nom de Dieu de putain de bordel de merde de saloperies de connards d'enculés de ta mère. You see, it's like wiping your *** with silk, I love it.
Wired: Your metal buttons wern't my favorite, but I don't really care who's skin I use. Others will be able to re-skin it later. I would love to see your transparent SKIN. I was working on one a bit myself today. Just rectangles with rounded edges and text in the middle. I made all lines 5 pixels wide, white in the middle, then gray, then black (so you can always see the button no matter what color is behind it).
I need more than just buttons though. I need frames kinda like TJ's. I need a whole new main-menu (we will be hiding the iG Main-Menu and just sending it keys from our custom menu). I was actually thinking of just having 5 button on each side, and when you click the "Menu" button, nothing new appears, instead the text on all 10 of the buttons change to new functions. You would be able to navigate the entire tree this way and only show a new window on top of the map for the Enter screen with the OSK skin. This OSK skin will have to have a "frame" that goes around the Enter windows results list.
Im too lazy to read the whole thread, but if this is useful, you should be aware that AutoIT supports partial matches on window names... you do this by using 'Mode 1' switch...
Edit: 'Mode 2' does substring matching...
2002 Honda CR-V
Carputer progress: 90% [▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ -]
Spent so far: $1105.90
Download the NEXUS Skin for Centrafuse
...or even Listen to my music
Thanks JIT, but I need the handle in the program, not in the AutoIt script. I'm sure AutoItX has the same feature, but unfortunatly AutoItX is a total POS (at least when used in Delphi) so I cannot use it to find window handles.
Does anyone know if there is a Windows API function like FindWindow() and FindWindowEX() that will find partial matches? If someone can give me the API call I will add it to SKINbedder V3. Otherwise I will figure it out later in v3.1.
Hmmm... how are you planning to do this?Originally Posted by RPM_VR4
If its possible in VB, then its possible in DelphiOriginally Posted by RPM_VR4
![]()
Bookmarks