The code has shipped and is in 1.5.10, but is hard-coded off in .
Well, after installing XP64, I was vindicated — none of the VS.
NET IDEs will install on it, because they rely on the 32-bit .
One of the features I've been working on for 1.6.0 is the ability to do bicubic resampling in the video displays using hardware 3D support.
We've been using simply bilinear for too long, and it's time we had better quality zooms accelerated on the video card.
Coming back from the Peninsula there is a sign that says: "Emergency parking: 1/4 mile." Several people suggested disable the frame pointer omission (FPO) optimization and prevent inlining, but it also doesn't stop the compiler from using spill space if it needs to — which means you basically have to set up a stack frame anyway.
I've been trying for some time to get YV12 support working perfectly, but at this point it looks like a wash.
Some do that and have unused space betweeen the Cr and Cb planes (weird). And a few simply don't support it (lame but pragmatic). Unfortunately, no one seems to have bothered to ever define the YV12 format properly in this regard, and thus we have massive confusion.
First, I finally fixed the FAQ link from the program, and also updated the knowledge base for known bugs in 1.5.10.
NET Framework, which currently doesn't work under WOW32. VC6, with the pre-release VC8 compiler from the Windows Server 2003 DDK.
This is a bit clumsy since the VC6 debugger doesn't understand VC7 debug info, and certainly can't debug a 64-bit app, so I have to use the beta AMD64 Win Dbg instead, but at least I have the AMD64 build in the same project file as the 32-bit build.
Although I have it installed for some time now, I've been avoiding using Visual Studio . The incremental improvements in the compiler simply aren't worth putting up with the braindead, butt-slow IDE.