|
Drag and drop from the toolbox perhaps?
Controls can be dropped only on groups; you cannot drag a control directly to a tab or to the Ribbon.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
LOL - Notice how they put that statement AFTER the "Add controls to the groups" link. So you click the link, go to the controls section, and voila!, you're now confused.
If it's not broken, fix it until it is
|
|
|
|
|
|
IMHO MSDN is the best technical documentation I've used in the past 15 years.
Kevin Marois wrote: It lists all the controls you can add , but not how to actually add them!!!
That would only add clutter. Check out the properties, I'd guess there's something like a Controls collection.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: IMHO MSDN GOOGLE is the best technical documentation I've used in the past 15 years.
FTFY
If it's not broken, fix it until it is
|
|
|
|
|
Do you mean the search-engine that you use to search MSDN, CodeProject and SO, or did you mean their documentation?
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Correct! MSDN is the best developer guidance resource out there... It just takes an intermediate level of understanding of the language only.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
|
Huh? Not sure how you came up with that boatload of baseless assumptions...
My point is if you have a section called "Adding Controls", then it should also contain the part about dragging controls onto the tab.
THAT'S why I hate MSDN. I rarely use it, because the information is technically accurate but practically useless, it's not real world, and it's scattered all over the place.
If it's not broken, fix it until it is
|
|
|
|
|
I really do agree to your claim, MSDN has a function description for everything in their APIs but they don't show an example for everything.. and mostly they're just paragraphic notes for everything (and they are just too technical).
But that doesn't provide any base to hate them, learn the language you're going to use. Once that has been done, you will find MSDN the best resource for a developer. You can count on me on this one. 
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Quote: because the information is technically accurate but practically useless,
Doesn't this describe just about any "Help" you get from Microsoft on their products?
|
|
|
|
|
I don't like to admit it, much, but...I like MSDN.
It's not perfect (and some of it reads like the new-kid was given the job and pressed COMMIT without anyone reviewing it) - but I started with paper manuals, and MSDN is far, far better than those:
It's more up-to-date than a paper bookIt's searchableIt's portable - I can read it anywhere, the documentation for the first version of MFC was two foot thick!It's (mostly) got examplesIt's in there somewhere - even if it's not trivial to find, it's at worst a few minutes awayIt's freeNo, it's not perfect; yes, some of the examples are a waste of space.
But given the sheer volume of information, it does pretty well.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Try the java world for a while... It'll really make you appreciate MSDN.
I've always had a love/hate relationship with Microsoft, but there are a few things they do REALLY well...
* .NET / MSDN
* Office
Ok, a couple things... And yes, we all hate Excel/VBA, but that's usually because SOME people treat it as a bad development environment instead of a good spreadsheet with macros.
|
|
|
|
|
Ian Shlasko wrote: because SOME people treat it as a bad development environment instead of a good spreadsheet with macros.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I started dabbling with a ribbon app about a month ago, and ended up adding controls to the ribbon by coding them in XAML. It goes quite quickly once you get the hang of it.
|
|
|
|
|
I was doing some toolbar work a couple of weeks ago. I don't remember the actual function I looked up, but it was something like this:
This topic is included for completeness. For more detail see the source code located in the VC\atlmfc\src\mfc folder of your Visual Studio installation. 
Soren Madsen
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
|
About twenty years ago, I had the (dis)pleasure of using Novell's NetWare API documentation. Compared to that pile of stinking manure, today's MSDN is a model of organization and clarity.
Note also that Novell's API was much smaller than MSDN is today.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Gawd! I'd forgotten Netware - the setup guide was enough of a PITA, without the API... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Kinda like comparing VB2 to VS2013...
How did the 20 year old Netware API docs compare to the 20 year old MSDN?
Contrary to popular belief, nobody owes you anything.
|
|
|
|
|
Mike Mullikin wrote: How did the 20 year old Netware API docs compare to the 20 year old MSDN?
MSDN was much better!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Agree, some of the documentation is rather blunt. It just means you have to go hunting again! I'm old enough to remember receiving the MSDN library quarterly on CDs.  Back then, it kinda sucked to have to give up a couple of Gigs of precious disk space, but it was better than finding/swapping the CDs. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
I totally agree. I'm that old too, so I also remember.
I've found that MSDN is nice for looking at object models, property, method, event lists, etc. But for h0ow things actually work, Google is your friend. In MSDN their "example" aare pretty useless.
I find that a lot of the time, whatever I'm trying to do someone else has already done, so a few minutes of Googling usually gives me a concrete answer.
If it's not broken, fix it until it is
|
|
|
|
|
http://www.fin24.com/Economy/INFOGRAPHIC-Zuma-earns-more-than-most-world-leaders-20150311[^]
At the bottom of this article are two interesting charts, showing the GDP and GDP per capita for some countries.
Points that I found interesting:
1. The high GDP per capita of the UK: Higher than that of Germany as well as Japan! Well done Brits!
2. The weak performance of Russia.
3. Despite the phenomenal growth in the GDP of China its GDP per capita is still pathetic.
By the way: The salaries of world leaders are shown in South African Rands. One SA Rand is worth about 9 US cents, due to that country's economic mismanagement over the past 50 years.
|
|
|
|
|
Cornelius Henning wrote: One SA Rand is worth about 9 US cents, due to that country's economic mismanagement over the past 50 years.
Woudl that be SA mismanagement, US mismanagement, or both?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
In the mid-1970s one SA Rand was worth 145 US cents. Today it is 9 cents. I do believe that says it all! 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
