VC++ GUI reference

Hi everyone
I'm new here. I've been learning C++ over my holidays and thought I'd start using the GUI side. I'm using the form designer in MSVC++ express edition. I followed the video tutorial on Microsoft's site and understood it, except the part where the person suddenly typed things like "label1->Text=String::Format("Choose a date {0}", dateTimePicker1->Value);" and "Application::exit()" etc. I understand what these do, and using them seems pretty self-explanatory. However, does anyone know where I can find a nicely laid out list/reference of these GUI commands and their parameters?
Thank you

http://www.google.com/search?hl=en&q...=Google+Search
http://www.google.com/search?hl=en&l...al&btnG=Search
http://www.google.com/search?hl=en&s...amming&spell=1
http://www.google.com/search?hl=en&l...al&btnG=Search

oh! Almost forgot. There's also this one:

http://www.google.com/

Erm, thank you for your 'amusing' post. However, I think you've missed the point entirely. I'm quite familiar with google, believe it or not, and I didn't find this website by randomly typing cprogramming.com . You seemed to have linked to another bunch of links that have tutorials on creating a GUI. Could you kindly point out, where in your post, you answered my question?
Thank you

> Could you kindly point out, where in your post, you answered my question?

on the last link

>> does anyone know where I can find a nicely laid out list/reference of these GUI commands and their parameters?

Erm ... what's that place called again? Google? If anyone can find it Google can! That's if Google's a person though.

Ok. I fail to see the point of a message board if google can find all. Anywho, care to suggest what I should type in?
http://www.google.co.uk/search?hl=en...G=Search&meta=
http://www.google.co.uk/search?hl=en...e+Search&meta=
http://www.google.co.uk/search?hl=en...G=Search&meta=

Google is not the answer for this. MSDN is.

http://msdn2.microsoft.com

> Ok. I fail to see the point of a message board if google can find all.

The message board is not for people to search for you. It is for them to help you solve specific code problems. This is not a google message board.

> Google is not the answer for this. MSDN is.

Which he would have found through google, had he at least tried.

Originally Posted by Mario F.

Which he would have found through google, had he at least tried.

Which search terms would you have searched for, being him. He described it as a function list/reference. He didn't know what it was called, obviously. An annoying forum troll is all that you are.

I dont even know how to reply to this...

Should I start from the fact the very editor he is using has facilities right there in the help menu that link directly to MSDN?

I really have no more time to give this thread. Excuse me while I close the door.

I don't know of a good, complete, WinAPI reference. I would expect a good reference to have all of the functions listed in alphabetical order and cross-referenced by function-purpose, with examples for each one.

The book Programming Windows, by Charles Petzold, is 'nicely laid out'. But, its style is more of a tutorial than a reference. It does make a good reference, but it's not complete (it doesn't have every Windows API function).

Your compiler's help files are a complete reverence (all of the WinAPI functions). But, there is not much in the way of tutorial help or examples. And, its not easy to browse if you don't know exactly what function you're looking for.

Of course, MSDN is the most complete reference. But I wouldn't say it's nicely laid out!

It isn't really fair to say "Just search google". It's like telling someone who doesn't know how to spell a word to look it up in the dictionary....you aren't necessarily going to find it unless you already know how to spell it.

So let's be fair here. What you want is to see documentation for the .NET Framework. Most of the windowing stuff is under the namespace Windows.Forms, but there's quite a bit of other stuff found in other namespaces that exist under the System namespace. This is all documented very well on MSDN. You can google for ".NET Framework Reference" and it should give you a MSDN link somewhere near the top.
Now, the .NET Framework is absolutely huge. It's a massive undertaking to learn. The docs are pretty good--I think better than previous MS frameworks, because there is lots of example code. BUT: The example code is typically in VB.NET or C#. They for the most part do not give c++ examples. So it's sort of up to you to covert the C# into c++, which might be a project in itself...

@Mario F - Do you not have the time, or have you turned your back on this thread because you've realised your comments were very unhelpful? I'm not sure if you've noticed, but none of your links result in MSDN appearing either. hmmm. For someone with the number of posts you've aquired, one would assume that typing "use MSDN" wouldn't be beyond your capabilities. It would've proved much more useful.

> The message board is not for people to search for you. It is for them to help you solve specific code problems. This is not a google message board.

Oh okay. I don't recall asking anyone to search for me. I just thought someone on a C/C++ forum may know of some site or resource. And by your logic, a LOT of posts on this message board shouldn't be here.

@Everyone else:
Thank you for the help. MSDN seems to have exactly what I want, just buried within a mass of things I dont . However, it does seem like the best resource available. After a bit of searching, I'll get used to the layout. I remember I looked at MSDN when I first got in to C++ but it was a case of knowing what command you were looking for, so I didn't delve deeper. So I guess in that sense, it was partly my fault for not looking more carefully.
Thanks again!

>MSDN seems to have exactly what I want, just buried within a mass of things I dont
Yes, and the search for MSDN bites as well. At the risk of sounding like another whiner that you didn't use google, at work I and my colleagues always use google to search MSDN instead of MSDN itself. It's much faster, especially if you aren't quite sure what you're looking for.

>another whiner

just.. precious.