[Release] SKINbedder BETA 2.99999

**RPM_VR4** · 07-25-2005, 04:11 PM

There's not a seperate button to activate the OSK... the OSK is just part of the skin for the "Enter" window. Every window will have it's own skin.

What do you mean RunWait() is part of the API. Do you mean there is a ShellExectute function that waits. I couldn't find one. Can you get me the name of it?

**0l33l** · 07-25-2005, 04:22 PM

Originally Posted by RPM_VR4

There's not a seperate button to activate the OSK... the OSK is just part of the skin for the "Enter" window. Every window will have it's own skin.

What do you mean RunWait() is part of the API. Do you mean there is a ShellExectute function that waits. I couldn't find one. Can you get me the name of it?

Yeh, I meant that say the Enter button will load up the skin for the Enter window, which will launch the OSK. The OSK will not hog up a lot of resources because its only going to be 2-3 image files.

WaitForSingleObject. I think that should do the trick. Its in the Windows class in Delphi.
Link
Code to wait till application terinates

**RPM_VR4** · 07-26-2005, 02:57 AM

Both of those use CreateProcess rather than ShellExecute or ShellExecuteEX. I don't really know much about which to use when and where (remember I used WinExec LOL). Sould I make my own using ShellExecute and WaitForSingleObject, or should I just use one of those with CreateProcess? Do you understand what the difference is and know which would be better for our use?

**0l33l** · 07-26-2005, 03:15 AM

Originally Posted by RPM_VR4

Both of those use CreateProcess rather than ShellExecute or ShellExecuteEX. I don't really know much about which to use when and where (remember I used WinExec LOL). Sould I make my own using ShellExecute and WaitForSingleObject, or should I just use one of those with CreateProcess? Do you understand what the difference is and know which would be better for our use?

No clue on the differences, but first make sure that that's the code that we want. It would suck rewritign a lot of the app to find out that it doesn't work properly

BTW: Take the code with command line parameters

**RPM_VR4** · 07-26-2005, 05:28 AM

I got it embedding perfectly every time now. I made my own ShellExecWait(CommandLine) function. It uses your ShellExecuteEX method but I tweaked it a little. It then calls WaitForSingleObject, but when I set its timeout to "INFINATE" (which is how it was in both of the things you linked to), for some reason the AutoIt script doesn't run for 20 seconds. I fixed it by continually calling WaitForSingleObject with a 1ms time-out and doing an Application.ProcessMessages in between each call. Now it works great!

Code:

//--- ShellExecWait ----------------------------------------------------------\\
procedure ShellExecWait(CommandLine: String);
var
  ProgramSEI: TShellExecuteInfo;
 begin
  with ProgramSEI do
   begin
    cbSize := SizeOf(ProgramSEI);
    fMask := SEE_MASK_NOCLOSEPROCESS or SEE_MASK_DOENVSUBST or SEE_MASK_FLAG_DDEWAIT;
    Wnd := Application.Handle;
    lpVerb := '';
    lpFile := PChar(CommandLine);
    lpParameters := '';
    lpDirectory := PChar(ExtractFilePath(CommandLine));
    nShow := SW_SHOWNORMAL;
    hProcess := Application.Handle;
   end;
  ShellExecuteEx(@ProgramSEI);
  while (WaitForSingleObject(ProgramSEI.hProcess, 1) <> 0) do
    Application.ProcessMessages;
 end;
//--- End ShellExecWait ------------------------------------------------------//

I think it will automatically work with parameters passed at the end of the CommandLine, but I will test it out and add a parameters variable if needed.

**0l33l** · 07-26-2005, 05:31 AM

Originally Posted by RPM_VR4

I got it embedding perfectly every time now. I made my own ShellExecWait(CommandLine) function. It uses your ShellExecuteEX method but I tweaked it a little. It then calls WaitForSingleObject, but when I set its timeout to "INFINATE" (which is how it was in both of the things you linked to), for some reason the AutoIt script doesn't run for 20 seconds. I fixed it by continually calling WaitForSingleObject with a 1ms time-out and doing an Application.ProcessMessages in between each call. Now it works great!

Code:

//--- ShellExecWait ----------------------------------------------------------\\
procedure ShellExecWait(CommandLine: String);
var
  ProgramSEI: TShellExecuteInfo;
 begin
  with ProgramSEI do
   begin
    cbSize := SizeOf(ProgramSEI);
    fMask := SEE_MASK_NOCLOSEPROCESS or SEE_MASK_DOENVSUBST or SEE_MASK_FLAG_DDEWAIT;
    Wnd := Application.Handle;
    lpVerb := '';
    lpFile := PChar(CommandLine);
    lpParameters := '';
    lpDirectory := PChar(ExtractFilePath(CommandLine));
    nShow := SW_SHOWNORMAL;
    hProcess := Application.Handle;
   end;
  ShellExecuteEx(@ProgramSEI);
  while (WaitForSingleObject(ProgramSEI.hProcess, 1) <> 0) do
    Application.ProcessMessages;
 end;
//--- End ShellExecWait ------------------------------------------------------//

I think it will automatically work with parameters passed at the end of the CommandLine, but I will test it out and add a parameters variable if needed.

Sweet! And I hope it positions perfectly too

**RPM_VR4** · 07-26-2005, 06:16 AM

Yep, as long as you wait for the AutoIt script to complete so that the iGuidance map window is visable before you embed it, then it is embedded, positioned, and sized perfectly everytime.

I added this code to the above procedure which make it automatically extract parameters from the CommandLine variable:

Code:

  CLParams: String;
  PrevSpaceIndex: Integer;
 begin
  CLParams := '';
  while not(FileExists(CommandLine)) and (pos(' ', CommandLine) > 0) do
   begin
    PrevSpaceIndex := pos(' ', CommandLine);
    while (pos(' ', copy(CommandLine, PrevSpaceIndex + 1, length(CommandLine))) > 0) do
      PrevSpaceIndex := PrevSpaceIndex + pos(' ', copy(CommandLine, PrevSpaceIndex + 1, length(CommandLine)));
    CLParams := copy(CommandLine, PrevSpaceIndex + 1, length(CommandLine)) + ' ' + CLParams;
    CommandLine := copy(CommandLine, 1, PrevSpaceIndex - 1);
   end;
  if (CLParams <> '') then
   begin
    CLParams := copy(CLParams, 1, length(CLParams) - 1);
    if not(FileExists(CommandLine)) then
     begin
      CommandLine := CommandLine + ' ' + CLParams;
      CLParams := '';
     end;
   end;

The only drawback is that if you do use CommandLine parameters, you also have to have the full path ("explorer.exe" will work, and "c:\windows\explorer.exe c:\" will work, but "explorer.exe c:\" would not work). I can live with that.

EDIT: Since I am now using ShellExecuteEX, you can run .au3's or any file with a shell association now too. Yay! Now that I have the embedding down, I am ready to get back in to button-code. I'm finally making progress with V3. This will be soooo much better than the previous SKINbedder versions!!!

PS: I'm still looking for a SKIN artist to work with if we are going to release V3 with all the iG sub-menus pre-SKINNED.

**d_sellers1** · 07-26-2005, 08:15 AM

Been away for a while. Glad to see you guys keeping up the good work without me. I've played around a bit with BETA 2.5 and it took forever to get the screen set right, but I got it.

One thing that I want everyone to take note of that I hadn't seen mentioned, is that you really need to determine your nudge and window settings from within the program you're gonna be running (ie., CF or RR). Just because you get it set right in Sb doesn't mean it's gonna embed properly in your frontend. I have two Sb BETA 2.5 folders; one for RR and one for CF since they needed different window and nudge settings.

Can't wait for BETA 3.

Derek

**camsgs3** · 07-26-2005, 11:00 AM

Originally Posted by RPM_VR4

PS: I'm still looking for a SKIN artist to work with if we are going to release V3 with all the iG sub-menus pre-SKINNED.

Where are you PS guys!!!

Cant wait for Beta3

**0l33l** · 07-26-2005, 01:06 PM

Originally Posted by RPM_VR4

Yep, as long as you wait for the AutoIt script to complete so that the iGuidance map window is visable before you embed it, then it is embedded, positioned, and sized perfectly everytime.

I added this code to the above procedure which make it automatically extract parameters from the CommandLine variable:

The only drawback is that if you do use CommandLine parameters, you also have to have the full path ("explorer.exe" will work, and "c:\windows\explorer.exe c:\" will work, but "explorer.exe c:\" would not work). I can live with that.

EDIT: Since I am now using ShellExecuteEX, you can run .au3's or any file with a shell association now too. Yay! Now that I have the embedding down, I am ready to get back in to button-code. I'm finally making progress with V3. This will be soooo much better than the previous SKINbedder versions!!!

PS: I'm still looking for a SKIN artist to work with if we are going to release V3 with all the iG sub-menus pre-SKINNED.

Sweet! We don't really care if you need to enter the directory, because most people enter in the full directory anyways

PM WebDog about the skin. He can make us a OEM looking skin, and that would be perfect