Simply make sure that both the boot screen and the process bar share the same palette, with the same palette index. You can confirm this in photoshop by using the color table editor. -Ian
Please keep your use of the modification on the word 'the' to 'teh' to a minimum. The key is to slip it in when it's not expected. Otherwise, it's just not teh same.
Last week I was priviledged to see, first-hand, a lot of the new technologies going into the Longhorn. It was an incredible amount of information to absorb, and I came away from it feeling just like the first time I saw the movie "Evil Dead" - impressed, and a little sickened. It all comes down to managed code. Now, before you go thinking "Oh, this is another one of those programmers who simply refuses to get with the times and move on to newer, greater, fuzzy things", please
nnnnnnnnnnoooooooooooooooooooooooooooooooooooooooooooooooooooo!!!!! heh.
...let me play among the stars... In this post I'm going to attempt to clear up all the murkiness around the Longhorn 3D desktop - hereafter known as the compositor, based on information that is currently public, but, as usual, subject to change. Chances are unless you work at Microsoft, or own a Mac, this article has been painted to a window on your screen using an aging technique. If you're running at a high resolution, it might be hard to read this text. If you resize
man that's annoying. Most users know pressing shift can avert an action.
Yea, we plan on doing some slick stuff when DesktopX 3 comes around! And yes, shaders are looking to be a part of the technology. For tier 1, shaders are required. For tier 2, 2.x shaders are required. As far as shaders are concerned, everything I've heard says they'll be applyable, to custom, mesh-based windows. Also, pixel shaders will apparently be used for a better version of cleartype. Some videos of the technology at an early stage: http://pc.watch.impress.co.jp/d
After a lot of requests, we've decided to release a boot screen replacement for XP. We'd always been wary about doing this - conventional boot screen replacements hack the resources in ntoskrnl.exe. Not only is this bad because patching system files is just downright stupid, but also it can cause service pack upgrades to fail, because they use a crc on the file to figure out which version it is. But, this is Stardock, and we have our ways. This week I prototyped a driver that uses so
Because DesktopX extends the Desktop. We use the same technology for rendering DesktopX objects as we do the IconX icons. It's a technology thing.
a {text-decoration:none; } So everyone's been speculating about Avalon. It sounds like it's going to be really cool. Out of all the tidbits I've heard through various public sources, I think the following interest me the most: 1) No Message Pumps! One of the big issues with Windows GUI programming is developers sometimes get lazy(or don't have time to write properly-threaded code), so you end up with a program that does a large amount of work
I believe this is just a full screen flash inside of active desktop. Not really impressive.
Since part of this uses a stage of the video card that cannot be captured(even with the likes of hypersnap DX), a picture will have to suffice. [Message Edited]
Very cool. And yet Shrek invades my day again!
This is what happens when you don't keep up. Though I'm one to talk - I refuse to learn the underpinnings of .Net because I believe it's the Delphi-MFC-VB-VCL of the new millenium. :(
Awesome Joe!
I've been reading over the details for Microsoft's own secure computing effort - the Next-Generation Secure Computing Base (or NGSCB for short). It presents a lot of radical ideas as far as application security is concerned, including: CPU and memory controller changes to enable strong process isolation (each application has its own execution memory space) Changes to secure user input (keyboard and m
Dokt is certainly not the only one, we're in print quite a bit.
WinCustomize Forums
Too bad it's an nVidia.
Nice. I have a NeXTStation turbo color w/21" color display gathering dust, need to hook it up and play with it again.
WinCustomize Forums
A fix for the Norton-DXScript issue has been implemented and will be in today's build. -Ian
WinCustomize Forums
I grepped all the current source trees, there's no chance there's a "doh" in any of the plugins we released or DesktopX itself. Are you using version 1.97 or an older version? Also, could you please export and send me the theme ( [email protected] ). Thanks, and apologies for the inconvenience.
Nice one Phil!
ElectronicMan: WB4 fixes problems with 3d games, etc. We've worked pretty hard to make sure it's a lot more compatible.
Floyd: 1.92 *is* DX2, we're just not giving it a 2.x version number until it's ready. -Ian
Go Scott!
JoeUser Forums