Whenever you can invoke statement completion, you can also execute the Edit.CompleteWord command. This command will complete a word that is partially complete with no other possibilities. And if there are other multiple possibilities, the command will invoke statement completion.
#64 Keyboard Shortcut to Display Quick Info Tooltip
As you mouse over a method in the Editor, a nice tooltip (as seen in the image below) is displayed for you showing you general information about the method, parameters, overloads, possible exceptions, and other documentation pulled from the meta data about the method (including your custom comments/documentation). This video shows you how to enable the tooltip, without having to leave the keyboard.
[CTRL]+[K]+[I] Invoke Quick Info. The command is Edit.QuickInfo, in case your keybindings are different.
#63 Copy Paste Parameter Info from the Tooltip
Intellisence is great. It shows us a lot, and mostly at the perfect time. When parameter info is being displayed in a tooltip, did you know you can copy or paste this information? This video trick shows you how.
[CTRL]+[ALT]+[SHIFT]+[P] Paste the default parameter names directly into the function.
[CTRL]+[ALT]+[SHIFT]+[C] Copy the info for some other line (see the commented line in the picture. Copying the parameter info will put the function name and all parameter information onto the clipboard.)
#62 Display parameter info for a function
Intellisense is great – probably the greatest thing ever invented to help developers productivity. But ListMembers isn’t always what you want. If you have CTRL+Space embedded in your brain telling Visual Studio to “Show my what I can put here” you’re getting a ListMembers popup. What you sometimes want is a ListParameters Tooltip, and this video shows you how.
Press Ctrl+Shift+Space to display the parameter info. The command is Edit.ParameterInfo, in case you need to check the keybindings. To iterate through the possible parameters, press the down arrow to go to the next and up arrow to go to the previous.
WPF: To Screen Stack or Load On Demand ??
In WPF which is better, to Screen Stack, or Load on Demand.
By ScreenStack, I mean to load all the screen dynamically onto a stack, and then set the visible property of all to false, except the one you want displayed. Like a stack of pancakes, popping the current screen to the top when you want it displayed.
Or … Don’t load the screens in advance, and then Load the screen you want on demand.
Both work … but I’m looking for pros/cons here.
Maybe a combination of both? If this is the case, what screens would I want to keep on the stack, and what screens would I load on demand? Why?
Thank you for your feedback / opinions.