I need a path!!!

from WinCustomize Forums
I've posted this absolutely everywhere, and still not got a response from anyone. So I'll post it here again in the hope that fellow WindowBlinds skinners can help out.

When you create an 'Execute Command' titlebar button in a WindowBlinds skin, what does the path default to? For example, if I wanted a button to run 'wbconfig.exe', which is in the WindowBlinds directory, how would I go about doing so without specifying the entire path? The reason I don't want to use the whole path is because WB isntalls to a different directory on certain systems.

SkinStudio says that the path defaults to the WindowBlinds directory, but this is clearly incorrect as just entering 'wbconfig.exe' in the 'Command=' definition doesn't work.

I'm losing my hair by the second...
2,723 views 7 replies
Reply #1 from WinCustomize Forums Top
I wish I could help, AGGGG I don't know



Powered by SkinBrowser!
Reply #2 from WinCustomize Forums Top
I'm not sure if this will help but the default path is path=c:\windows; c:\windows\system32 on a clean install of XP and close to the same on 98...the only thing that will differ from one system to another is if they didn't use c:\windows as their install directory...but whatever they used will go to the same directory that holds those files...all other paths are created by software installs like Windowblinds or are user added.

Just use RUN ---> command and type path at the C:> prompt and your paths will be displayed.



Powered by SkinBrowser!
Siege of Centauri
Reply #3 from WinCustomize Forums Top
I was under the impression that WindowBlinds initially looked in a pre-determined path of its own before trying the system default paths.

This may not be the case however, as I've only managed to get files to run which are in the system default path.

It looks like I'll just have to hard-code paths into the UIS file and expect users to modify them themselves. Not the ideal solution, but seemingly the only one.
Reply #4 from WinCustomize Forums Top
Likely only the Stardock folks could tell you whether Windowblinds writes enviromental variables when it installs. But the hope would be that it does, and then you could call those variables rather than full paths.

In Litesetep yhr syntax for enviromental variables is like this:
$explorer$ ,as an example would launch windows explorer without having to put in the full path. In a purely windows interface and enviroment though I'm not sure how exactly the syntax would be.

There should be others here who can answer those questions.
Reply #5 from WinCustomize Forums Top
also keep in mind that on windows 2000 and XP you don't need to specify a path. Just the name of any exe using the Run cmd.



Powered by SkinBrowser!
Reply #6 from WinCustomize Forums Top
Isn't the current path the skin folder? So to reference WBConfig.exe from that would be:

..\WBConfig.exe

[Message Edited]
Reply #7 from WinCustomize Forums Top
Nope, that doesn't work MadIce. That's one of the many variations I've tried. Thanks for trying to help though.

The problem with your suggestion §tatic, as I noted in another thread, is that the 'execute command' buttons won't accept command line paramaters/arguments. Just typing 'wbconfig.exe' doesn't work, and 'run wbconfig.exe' won't work either.