New update available at the same location. Now allows you to specify colorisation settings and enable colorisation per skin.
pjpowell
OK. Latest version available has the ability to enable colouring per skin. Was simpler than I thought it'd be.
Erm. Do you have Skinstudio installed? If so please email me at [email protected] I need to troubleshoot if it's not working.
It's a Delphi app and uses the standard Delphi icon.
Apologies. I corrected it but WC has been having weird issues. I've corrected it my end now.
A very early build of my new WB Skin Randomiser is available at http://pjpowell.dyndns.org/Downloads/SkinRandomizer.exe This displays all your skins in a long list (main skins and subskins) and allows you to group and save the names to a file. Then you can load groups as and when you like and set the timer to change randomly between them. Bear in mind I only started writing this yesterday but any opinions/requests for features would be most welcome. This does require that Ski
I came across this post just as I was pondering making one myself. Reading this decided me. A very early build is available at http://pjpowell.dyndns.org/Downloadables/SkinRandomizer.exe This displays all your skins in a long list (main skins and subskins) and allows you to group and save the names to a file. Then you can load groups as and when you like and set the timer to change randomly between them. Bear in mind I only started writing this yesterday but any opinions/req
desktop shortcuts. The error you refer to is usually caused by iconx. Make a new folder on the desktop and move all the non-standard shortcuts off the desktop into that. Then try desktopx again.
In a few cases I have seen of this problem the cause has been a shortcut that iconx is having problems with. Resolution is fairly simple in those cases. Move all shortcuts to a temporary folder and try DesktopX again afterwards. If this works then move them back a few at a time to try and narrow down the exact shortcut. It's most likely to be one that was added immediately before it started giving errors. Once you track it down please send the info to stardock so they can see if the
These problems are usually caused by the windows scripting host being corrupted or damaged in some way. Try creating a normal vbscript file and running it. Chances are if this has happened that will not work either. You may need to reinstall the script host for your operating system. http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en for Win2k/XP.
There seems to be an issue with whether the taskbar is visible or not. DX seems to take it into account and moves objects accordingly.. The problem is that it seems to check it too early or something and positions things in relation to it before it realises it's hidden.
oops. Alternatively right click it and disable script. Then you get the handles anyway. Right click and re-enable the script when you have finished changing the size.
Pogs 3K: To resize controls in DX (web browsers, edit windows etc) you simply need to be in edit mode and hold Ctrl while left clicking the control. You should see the normal resize handles appear and you can size it however you wish.
Install Stardock Central which will install the Stardock MCP which handles the system tray. It sounds like for some reason it didn't get installed.
DesktopX has it's own show desktop option. Just make a new object with type of System and Show Desktop. Alternatively use Windows Key + M to minimise all windows and Shift+Windows Key+M to restore the windows.
I know the one you mean. It's called stellar I believe. Not sure where you can get it from though as it doesn't seem to be on this site. Maybe someone else will have it.
Free PDF writer at http://www.pdf995.com/ Slight caveat is that it opens a sponsor page on your web browser each time you print using it. If you can live with that it's free though. One alternative I have used is a postscript printer driver and ghostscript/ghostview to convert the resulting PS to a PDF file. This is genuinely free but more of a hassle to set up.
scottsh: I tend to have an edit control object called debugbox on the desktop and a sub like this: sub debugadd(texttoadd,clear) if clear=true then control.text="" else control.Text = Control.text & Vbcrlf & texttoadd end if end sub then in any object I use something like: DesktopX.ScriptObject("debugbox").debugadd("val1 = " & val1,False) if val1 = 3 then ' do something else ' do something else end if <
I found Blender too confusing for me so I bought 3dmax and have been learning that instead.
Of course I should say that I was on 17inch 1024x768 and 15inch 1024x768 monitors until last Monday.
I'm here from the 'we have large monitors and are proud of them' brigade. 22 inch beastie here 1280x1024 normally. 1600x1200 when using 3DS Max
Did it say on the first screen that both things had hardware support on c2? The numbers can be meaningless. Trust what your eyes see when that window moves on the screen is it noticably slower than on c1? If so then it may be drivers or the card itself. To be absoluteley sure it's to do with that (and I suspect it is)you'd need to slap it in pc1 and see if it has the same problems. That rules out everything lese and leaves something to do with the gfx card. Mi
Download the XPBench software https://www.stardock.com/products/xpbench/ and run it that should check if constant alpha blending and per pixel alpha blending are accelerated by your card. If they are then it's not the vid card the next thing is the internet connection. It might be an object in the theme that is using that might be worth gradually stripping the theme until it stops using so much cpu or at least disabling scripts until it stops using so much cpu <BR
as f0r3 says the graphical capability of the Pc has a lot to do with it. If you have a graphics card that can handle the alpha blending in it's own processor then it'll use much less cpu in taskmanager. If the cpu has to do all the work then it'll cause what you describe. What graphics card are in both? It's possible upgraded drivers or a driver tweak on the one that uses too much cpu would correct that problem depending on the card and memory. also the resolution and bit depth may have a pa
jafo: Technically it isn't as it just threw it out of the pram.