Raymond Chen also regularly recommends you to stick to well documented public APIs rather than relying on implementation details not meant for external usage.
The specifics of how the DWM operates aren't documented on purpose because they're implementation details that might change at any time and break any software that relies on them.
Do you really want to trade-off the potential that an update may break your software without prior notice in exchange for a small performance gain that may or more not actually be achievable? It may well be possible to do what you're thinking about, but that doesn't make it a good idea.
//EDIT: If you're just investigating out of curiosity then I wish you luck in your search, but if you're writing production software please don't inflict the world with more fragile software that might suddenly stop working.
Show differencesHistory of post edits
#2jbadams
Posted 10 October 2012 - 03:39 AM
Raymond Chen also regularly recommends you to stick to well documented public APIs rather than relying on implementation details not meant for external usage.
The specifics of how the DWM operates aren't documented on purpose because they're implementation details that might change at any time and break any software that relies on them.
Do you really want to trade-off the potential that an update may break your software without prior notice in exchange for a small performance gain that may or more not actually be achievable? It may well be possible to do what you're thinking about, but that doesn't make it a good idea.
The specifics of how the DWM operates aren't documented on purpose because they're implementation details that might change at any time and break any software that relies on them.
Do you really want to trade-off the potential that an update may break your software without prior notice in exchange for a small performance gain that may or more not actually be achievable? It may well be possible to do what you're thinking about, but that doesn't make it a good idea.
#1jbadams
Posted 10 October 2012 - 03:38 AM
Raymond Chen also regularly recommends you to stick to well documented public APIs rather than relying on implementation details.
The specifics of how the DWM operates aren't documented on purpose because they're implementation details that might change at any time and break any software that relies on them.
Do you really want to trade-off the potential that an update may break your software without prior notice in exchange for a small performance gain that may or more not actually be achievable? It may well be possible to do what you're thinking about, but that doesn't make it a good idea.
The specifics of how the DWM operates aren't documented on purpose because they're implementation details that might change at any time and break any software that relies on them.
Do you really want to trade-off the potential that an update may break your software without prior notice in exchange for a small performance gain that may or more not actually be achievable? It may well be possible to do what you're thinking about, but that doesn't make it a good idea.