Things that bug MadIce
Published on April 29, 2004 By MadIce In Skinning
If you are a skinner and interested in testing a new WB plugin then respond to this thread. No support for SKS yet. This is the description:
//====================================================================
// WBExec
// Plugin for Stardock's WindowBlinds
// Execute commands from the title bar
//
// Copyright (c) 2000..2004 MadIce
//
// Special thanks to
// - PJPowell
// - Hippy
// - Adam Najmanowicz
//====================================================================
// This documentation is for skinners not using Stardock's SkinStudio.
// That application provides user friendly support for WBExec. You
// cannot add WBExec to a WB skin without changing the skin.
//====================================================================
// WBExec can assign up to 3 functions per button. In the samples
// below we use Button #12, but any number will do and the plugin
// supports more than one button. In the samples below you'll need to
// change SkinName for the actual skin name you are using. Each button
// section needs at least tow entries:
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
//
// You can add any other valid WB declariations in the rest of the
// button section. In the samples this will not be shown.
//====================================================================
// 1. Execute a command
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExec=NotePad.exe
//
// In this sample NotePad will be started whenever the user clicks the
// button. Note that you don't have to specify a path. WBExec will try
// to find the application in the following order:
// - The skin folder.
// - The folder registered by the application.
// - The current path (using the Windows settings)
//====================================================================
// 2. Adding parameters to the command
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExec=NotePad.exe
// WBExecParams=SkinName.UIS
//
// The above sample loads the skin's UIS file in NotePad. It will find
// the skin file because no other path has been specified. Although
// you can specify qualified paths you shouldn't do so. The user may
// have another folder structure, or may not use drive C or the
// folders may have a different name when the user is in another
// country.
//====================================================================
// 3. Using Shift or Ctrl while clicking
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExecShift=NotePad.exe
// WBExecShiftParams=SkinName.UIS
//
// This sample is similar to the previous one, but instead of a normal
// click the user has to press shift while clicking the button. You
// can also specify the Ctrl key instead:
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExecCtrl=NotePad.exe
// WBExecCtrlParams=SkinName.UIS
//
// Of course you can combine these options. That means you can have up
// to 3 commands per button.
//====================================================================
// 4. The Drive menu
//
// You can show a menu which contains all the drives present on the
// system. Pressing an item on the menu starts Explorer and makes it
// show that drive.
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExecMenu=1
//====================================================================
// 5. The Folder Menu
//
// You can show a menu containing some common used folders. The number
// of folders depends on what Windows version has been installed and
// how the user configured it.
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExecMenu=2
//====================================================================
// 6. The Start Menu
//
// You can show the start menu by specifying menu option #3:
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExecMenu=3
//====================================================================
// 7. Mixing comands
//
// Like the other WBExec options you can specify whether the user
// needs to press Shift or Ctrl when invoking a menu.
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExecMenu=1
// WBExecShiftMenu=2
// WBExecCtrlMenu=3
//
// ... or ...
//
// [Button12]
// Action=-4
// DllName=SkinName\WBExec.dll
// WBExecMenu=1
// WBExecShift=NotePad.exe
// WBExecShiftParams=SkinName.UIS
// WBExecCtrlMenu=3
//====================================================================

Comments
on Apr 30, 2004
i don´t even use Windowblinds, just wanted to say this is pretty cool stuff. as it supports command line parameters this could be really used to extend window management when using it together with LiteStep or any other command driven desktop (send window to next desktop, keep window sticky on all desktops, etc.).

personally i think this is rather useful for individual use than for distributed skins. those launch buttons most people will do are nothing but bad interface design. to each it´s own i guess.

but overall: very cool.
on Apr 30, 2004
Thanks, Moshi.

It all started with an idea that Hippy had for a GUIO skin. It should do that well. The bells and whistles were added later to make it more attractive to other skinners.

The need for testers is rather urgent. It doesn't take much time to test. Drop it in the skin folder and modify an existing button. It would really help me to get some response.

Phil noticed that I should call this thread something like "Looking for skinners to test new WB plugin". But alas, I was a bit tired when I made the post.

Anyway... Let's see if it generates a response. If not then I am gonna release it sunday or so.
on May 01, 2004
Its still working flawlessly here MI
on May 01, 2004
Thanks, Snowman!!!

I''ll mail you a smaller build. Size decreased by 50%.

This message board is acting funny. It will not accept the word d.r.o.p.p.e.d. So I changed it for "decreased" Hehe.

[Message Edited]
on May 30, 2004
Just saw Tiggz use of it in , I think I'm going to replace the WBWinMenu button in the skin I'm making with this plugin.
on May 31, 2004
Madice, I want to thank you for your excellent plugin
One thing that I found didn't work for me, although it worked for someone who helped test my skin, was the object desktop menu. When I configured the button to show the object desktop menu, it just didn't do anything. No errors or anything like that, it just didnt work. Everything else I tried worked like a charm tho.
Thanks again

p.s. one of the really great things about this plug-in is the easy way you allow the user to configure the button. I use it to show the quicklaunch menu, then it's a cinch to configure a list of programs to appear in the menu
on Jun 08, 2004
Thanks guys.

About the ObjectDesktop menu: Whenever you move the ObjectDesktop menu in the start menu the plugin will be unable to find it. That's probably what happened to you.
on Jun 08, 2004
yeah, that sounds about right I do love to re-organise my start menu every now and then