3 ms·
I'll disagree there. After spending hours trying to make sense of the Win32 API documentation in msdn. Often failing to make sense of it, finding the answer in
by jpablo 11y ago
I'll disagree there. After spending hours trying to make sense of the Win32 API documentation in msdn. Often failing to make sense of it, finding the answer in Raymond Chen blog a long with a few lines pointing out that the msdn documentation doesn't cover some important cases/caveats.
- Alupis 11y agoDon't forget all of the undocumented API's which you are not to use unless you're a really big vendor then you get special documentation and/or special API's built just for you.
- ske4286 11y agoMost all Win32 stuff works just fine. It is documented better than _any_ one Linux module/layer. There is no comparison. But these days I don't even need to bother with Win32, .NET handles 99.9% of what I need to do. Then again I am not a driver developer.
- ultramancool 11y agoEh, some of it is a huge pain. I wanted to write a simple tool to mute a game when I tabbed out of it. No access to per-app volume controls from .NET without the use of some random paid libraries. So I went with C++. Access via C++ involved incredibly complicated COM APIs, which were very poorly documented (the whole COM system itself was confusing but these APIs in particular involved a ridiculous level of nesting) and no good clear examples were available. Easily more confusing than the simple calls into the DBus interface for pulseaudio to achieve the same thing on an Ubuntu desktop system.