I just uninstalled Adobe Reader X. Man that felt good.
In Windows Developer Preview, Windows Classic theming mode no longer exists, and UX theming mode has been modified to include support for high contrast themes. Also, the system now stores the current visual styles so that they are always available, even when the Themes service is not running. Because of these changes, applications that target only Windows Developer Preview no longer need two separate code paths to support visual styles and high contrast themes.
It’s crazy that the old Windows 95 widget support exists under the hood of every Win OS up to Windows 7. As a developer this presents added work in insuring support, especially in projects like Mozilla, which handle common control theme rendering internally. I can’t believe it’s taken this long for MS to kill Classic off – this is great news. Good F’n riddance!
Ever get an exception when enabling feed synchronization from the feed api?
IFeedsManager fs = new FeedsManagerClass();
Exception: Task image is corrupt or has been tampered with. (hresult:0x80041321)
I’m not entirely sure what causes this, but basically the background task schedule job has become corrupt. The simple fix:
1) open an elevated command prompt
Which deletes the old task and then recreates it.
Neat, and fast. Link.
Berry, Beetle, Apple, and Puma.
We have a long way to go.
Use RedrawWindow w/the RDW_FRAME & RDW_INVALIDATE flags and pass a region in hrgnUpdate that includes the non-client area you want to repaint. Note, hrgnUpdate must be in client coordinates, not screen coordinates. So for example if you’re invalidating the left hand frame, the x origin will be a negative number, equal to GetSystemMetrics(SM_CXFRAME).
“This is mind-boggling. There’s no possible technical justification for this. It’s pure evil.”
OOPP – A very intertesting project. Still lots of work to do, but it’s coming along.