Full of sound and fury, signifying nothing.
Peter's a topic stealing stealer person. So rather than pout about how he's stolen my thunder, I'll just add some lightning for effect. I'm a fan of the closing paren' being on the line with the last value. Not on its own line. I mean what does this really buy you?
hr = m_Device->GetFxDevice()->CreateIoQueue (
callback,
Default,
DispatchType,
PowerManaged,
FALSE,
&fxQueue
);
It's always driven me nuts. Seriously, like the braces thing, it just looks unbalanced and it just takes up a line. Sure in ye olden tymes of low resolution monitors, it was an aid, but we're in High Definition land now kids, let's start acting like it! ;) Add to that the German / Vulcan in me says if you're going to get all Obsessive Compulsive about where the close paren' lives, then it should really look like this -
hr = m_Device->GetFxDevice()->CreateIoQueue
(
callback,
Default,
DispatchType,
PowerManaged,
FALSE,
&fxQueue
);
Nope, this is how I roll -
hr = m_Device->GetFxDevice()->CreateIoQueue (
callback,
Default,
DispatchType,
PowerManaged,
FALSE,
&fxQueue);
And yes, it does drive some of the WDF people crazy because they still hold on to some of the old coding styles, but that's just tough. :P
There's really only one old style convention I try to hold to from my college days. Not charging past 80 characters in width. I find that using that line today helps me page face source files on a 16:10 monitor. And at home on my 24" 16:10 monitor, there's enough space to keep the solution explorer open and docked to the environment as well.
A few people have also asked how I got the blue line down the margin of my code, fairly simple really. It's a registry addition -
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\%VERSION%\Text Editor]
"Guides"="RGB(0,0,192) 80"
Make sure you replace %VERSION% with your Visual Studio Version (2005 is 8.0, 2008 is 9.0).
*Currently playing - Eric Johnson, Desert Rose