It's been a long, long time since CClock was last updated back in May 2000. I don't even know if the author is still around the WB community. So unless someone wants to code a new clock plugin, I think we're stuck with the problem on XP. I agree that the 'centralized plugin folder' idea would work well. For the moment though it's not too big a deal to simply update the skin download with a new plugin should one come along.
In the meantime however, I think the 'rough estimate' clock still serves a good enough purpose to include in skins.
I've spoken to Neil, and he agrees MadIce. Hopefully the WBAmp problem should be fixed in the next build of WindowBlinds, but the CClock problem is to do with the way it interfaces with WB on WinXP and needs to be fixed in the plugin itself.
Good work for today T-Man. Go get some rest and worry about the rest tomorrow.
Damn, and just when we managed to get her vital signs stable again. The doctor will be on call for the rest of the day. Good luck!
I saw this skin over at DevArt too. I really can't believe that someone can 'forget' whether a piece of work is their own or not. Unless of course you're that guy from 'Memento'. Either you have the original source files for the images or you don't. It can't be that difficult to remember.
I've already posted this in the newsgroups, but they seem to get very few visitors these days. On my continuing quest to re-aquaint myself with the WindowBlinds skinning engine, I've been checking out my old skins with WB4. As all of my skins use both the WBAmp and CClock plugins, I was rather dismayed to see that neither seem to function correctly with WB4. Firstly, with WBAmp, when creating a song title 'button' with an image background, all that seems to be displayed is a so
*wump!* Okay, we've got a pulse. Looks like she's back. That was a close one folks. Take it easy now WinCustomize. It was touch and go for a while there. Get some rest.
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.
I'm still around, and all I'll say is keep your eyes open.
You can't go... because... I'm your twin brother!! DA-DA-DAAAAAAAA Anyway, if you leave, the curse will kick in that got passed on to you when you found that mystical gem in a forgotten Egyptian tomb after the cruise liner you and every other person in your town was travelling on went down and stranded you on an island where you lived off of cocunuts for ten years.
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.
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 be
Are you trying to blind us Jafo??
Which reminds me... I must make sure to put the plant pot and hatstand in at some point.
I wish I didn't need to sleep, and that my eyes didn't hurt so much.
You'll just have to wait for the upload I'm afraid, and that won't be for a couple of weeks yet. Things will probably change a lot by then too, so take that list as a starting point rather than a final features list. The purpose of this thread was more to get an idea of what people would like rather than a chance to plug a half-finished skin. So keep the ideas coming!
Patience young Jedi, patience.
I listed a WinMenu button joe! They all fit on the titlebar without any complicated expanding bits to add another mouse click to the process. I've managed to find what I think is a quite unobtrusive and logical method of displaying icons which are used less often than the main titlebar buttons. All of these buttons (currently) fit on the smaller windows you'll encounter too, which was one
Strapped?
What you're referring to isn't a 'throbber' at all goodmorphing. You're just seeing animated buttons, which are moderately easy to make in a skin, but don't have anything to do with the Explorer throbbers.
I'm not missing manni. It just takes me about a year to create a skin.
Not forgetting the hidden 'Global Descruction' button. No random clicking now please.
Damn... it keep falling off the wall. Anyone have any superglue?
And yes, this does mean I'm skinning again, but that's all I'm saying for the moment.
WinCustomize Forums