§ ¶Archos MPG4 Translator incompatibility with 1.6.x fixed
Archos has informed me that they have just released version 3.0.12 of their MPG4 Translator tool, which resolves the command-line compatibility problem with the 1.6.x series of VirtualDub. Yay!
Now, if I can only get the Visual Studio .NET team to fix their horribly broken Win32 resource editor....
What's wrong with Visual Studio .NET resource editor? :-?
alex_t (link) - 09 08 05 - 14:46
It randomly changes symbolic constants such as IDC_MOVEUP to their numeric form, so that the next time you open a resource you see a menu command that's tied to 39472. I encountered this bug when I tried using Visual Studio .NET 2002 and one of the reasons I moved back to VC6 was that I was tired of VS.NET's resource editor silently breaking my .rc files. As far as I'm concerned this makes the resource editor unusable, but even worse is that it's still in VS2003, is still
in VS2005, and is being triaged as Won't Fix for that product:
Never mind the fact that the new property grid style is much less usable than the VC6 resource editor.
Phaeron - 09 08 05 - 23:58
You'll be happy to know that the bug you list above was reopened and now reads "Fixed".
Paul - 16 08 05 - 00:59
Hmm... if this keeps up I might have to fix something myself. :)
Phaeron - 16 08 05 - 01:22
Please keep comments on-topic for this entry.
If you have unrelated comments about VirtualDub, the forum is a better place to post them.