Thread: [Release] SKINbedder BETA 2.99999

Originally Posted by 0l33l

Well, if the titlebar changes constantly, then why not try and embed it based on its class name?

Net Stumbler does this, because every time it runs it creates a new file with a different name, and the file name is part of the titlebar.
All you have to do is make sure it always opens the same file. Just save it with a name you like in the Net Stumbler folder and the open it as a parameter. Like "C:\Programas\Network Stumbler\NetStumbler.exe myns1.ns1" .
In this way, the titlebar will always be "Network Stumbler - myns1.ns1" ( or "Network Stumbler - [myns1.ns1]" if the child window is maximized, but its ok since at that point it is already embedded in SB).

The side effect of this, its that it wont "auto scan" so you will have to start scanning by sending ctrl+s witch is very easy with AutoIt .

Originally Posted by Bravellir

Net Stumbler does this, because every time it runs it creates a new file with a different name, and the file name is part of the titlebar.
All you have to do is make sure it always opens the same file. Just save it with a name you like in the Net Stumbler folder and the open it as a parameter. Like "C:\Programas\Network Stumbler\NetStumbler.exe myns1.ns1" .
In this way, the titlebar will always be "Network Stumbler - myns1.ns1" ( or "Network Stumbler - [myns1.ns1]" if the child window is maximized, but its ok since at that point it is already embedded in SB).

The side effect of this, its that it wont "auto scan" so you will have to start scanning by sending ctrl+s witch is very easy with AutoIt .

thank you I did'n think about this

I hope it will support an hidden window title bar

Originally Posted by RPM_VR4

I don't think you can embed on class alone. Not unles FindWindow('<classname>', '') will work even if the title isn't blank (''). How do people make it find partial string? Do you have to step through each running process and look for a partial match? Ol33l: Is that what you were doing with iGSkinner before in order to make sure you have the correct blank ('') window to kill the nag?

On a sadder note, AutoItX sucks! It will not run AutoIt scripts at all, even when they are compiled to an exe??? Also, you can NEVER pass ANY of its functions a blank string (''). That means you can't use it to open INI files if you need the default string to be blank ('') and you can use it to find window handles or click controls where the control name or containing window title is blank (''). I had a very frustraiting night on Friday when I was working on it.

I did get the Win API api calls to remove a title bar and embed fairly perfected (I think), so hopfully this embedding in the lower right bug will go away for good, and I shouldn't have to re-embed on a timer which will prevent buttons from blinking all the time.

Now I need to revert all my new AutoItX code to our old INI and ShellExecEX routines. This will allow it to run AutoIt scripts, unfortunatly it will not be able to perform basic AutoIt functions within it's own thread, so it may be easiest to make it so EVERY button will have to use an AutoIt script (of course, iG's will come pre-setup in exe form so you wouldn't have to install AutoIt unless you wanted to change something or to make a "skin" for a different program). Does this sound good all you guys (our users), or would it be better to give SKINbedder some basic API powers without having to make an external AutoIt script (ie: Launch Programs, Send Keys, Control Clicks [with no blank titles])?

Well, you can do FindWindow('CLASSNAME', nil). That'll find the first window with a blank classname.
Its ok that we are moving a bit away from autoit.

Originally Posted by RPM_VR4

Ol33l: As soon as you run iGuidance, both the Nag window and the main 'iGuidance' window are findable (FindWindow('IntellinavWCls', 'iGuidance') returns a value even though it is not visable until you click the nag). Also, even after you click OK on the nag and it goes away, FindWindow('#32770', '') still returns a value. If you embed the iG window before it is visable, then you get that problem with it being in the lower right instead of at 0,0 or nudged even further. So the question is: If an AutoIt script is doing the nag killing, how can I tell when it is done and the main iGuidance screen is visable?

BTW: If AutoItX's RunWait() command worked this wouldn't be a problem, but for some reason if you use AutoItX's RunWait() to run an AutoIt script (even a compiled one), the program just waits forever because the AutoIt script never does anything nor closes. The AutoItX Run() command works, but then I have no way of knowing when it is done and the iGuidance map window is visable. If I use a Delay(500) it works great, but I want it to happen as soon as possible and reliably, so using a configurable Delay() is not the best solution.

I need to be able to find out 1) If the AutoIt Script is done, 2) If the iG map is visable, or 3) if the nag is not visable (any of the 3 indicate that we are ready to embed).

Yeh, it will find the iG window even if we can't see it. I used to do that to check if iG was running
I think that there is code to do a run and wait. AutoIt is just a collection of APIs.

Originally Posted by camsgs3

Hey RPM will SB 3 have osk support for IG or will that come in a later version

looking foward to Beta3

Dunno
I'll try to peice something to gether with VisualDesigner and XML

I'm pretty sure that there is an API for run and wait till it executes. I do like your solution though

Originally Posted by RPM_VR4

Can you find it for me? How would it work, just look checking the process list to see if whatever it just launched is still open or not?

Anyway, I started creating a bunch of utility functions to use instead of crappy AutoItX. (Note: AutoIt is cool and we will still use it, it's just the ActiveX varsion of it that sucks.)

Code:

FindWindowHandle   (with class optional. I will make name optional too)
WaitForWindowHandle     (with time out)
EmbedProgram(ProgHandle, ContainerHandle, X, Y, Width, Height)
                           (which also removes the title bar & boarder)
Control Clicking Stuff
Sending Keys
INI stuff
XML stuff
Reg stuff

PS: An OSK will be possible in V3 (but maybe not included). It will probably slow down the PC a ton until we figure out a way to use JPGs or just to have one GIF image instead of one for each key. The OSK will be perfected in a future release.

I will work off my code to add the OSK. Then we'll have a button to activate the OSK