Comment #2 Wednesday, August 29, 2007 2:36 PM
I was wondering what was eating up resources, thanks for pinpointing it for me. If I'm ever inclined to play with the object again, I'll try and implement the things you've suggested to make it less resource intensive.
This was actually inspired by a X11/MacOS screensaver called Phosphor by jwz which looks a lot better than mine and comes complete with long sustain phosphor emulation. You could probably get his to display system stats if you wanted, though I don't think there is a windows version.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading files.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
Comment #1 Saturday, August 25, 2007 6:27 AM
I like the way you created the interlancing of the text.
Changing text objects in DX is painfully resource intensive. For instance, if you're compiling allot of text in a script, it's better to assemble all the text in an variable before outputting it to a textobject.
However, when it comes to this kind of thing where you simulating the text being written there's not much you can do. The only thing I can think of is maybe setting the width and height of the text object to hide parts of the text and slowly increase the width to expose one character at the time. That way you might save some CPU power as it won't have to render the text all the time. Only a theory though.
This would be nice as a screensaver. All you need to do is add support for the arguments sent to screensavers so it knows when to start. Then compile it as an .exe and rename it to a .scr.