I am talking about the programming interface ArkM, it is drag and drop just like VB.

I didn't say the syntax was the same, I'm not blind or stupid. And I am insulted that you seem to think I am.

I'm out of this thread, tired of being treated like a dumbass. I get enough of that already.

>I am talking about the programming interface ArkM, it is drag and drop just like VB
>I'm out of this thread, tired of being treated like a dumbass.
I hope now you will have a time to read Qt documentation: Qt Creator (probably it's that damned drag and drop interface) is an optional tool in Qt SDK. You (and me) can create Qt GUI applications without any visual add-ons...

QT Creator, as ArkM said, is optional. Just like GLADE for GTK+. And it is no-where VB-like. When we say a thing X is Y-like, usually Y is the pioneer and X has inherited from it. This is not the case with VB.

>I have every single source code file of the windows API, provided by Dev-Cpp
>under the Open Source lisence.
The file you posted is the definition my dear, not the implementation file. Implementation file comes compiled from the OS provider(M$) and thus you won't find its source code.
BloodShed Dev- Has provided you with the definition file so that you can see what all interface is available to you.

>What if everybody didn't know how to hard code, and always used QT?
>Nobody would actually know how to use C++ in its native form, only being
>able to code with help from a program that provides indirect functionality.
Fine, then stop using the STL. Stop using the windows.h and program everything yourself. Stop using the compiler, hard code yourself. Stop using your OS, hard code yourself. Would you?
Look, if your with hard coding, open-source toolkit will provide better control.
I used GTK+ in which I usually had to hard-code( Though, I never felt I was hard coding) while I was making a C app. Here is a Hello World:
[I realized that posting the code would make the thread bloated so here is the link for the same http://library.gnome.org/devel/gtk-t...SEC-HELLOWORLD ]

>People should learn multiple APIs and kits.
Very Bad advice. Cross platform toolkit are invented so that you can stick with the famous Unix philosophy " Do one thing; and do it well."
There is no point in learning every other native library for different platforms. Rather Master one cross-platform library ( like wxWidget, QT or GTK) and stay happy.

>If you dont know what is inside, then it is more difficult to utilise its full potential.
Many great programmer don't know whats inside STL, yet they utilize its full potential. This is the key to abstraction.

>All I am saying is if you are ACTUALLY serious about programming then use
>something that doesn't do everything for you.
Fine. So, do you know what is running behind the WInAPI. You cannot, since it is not open source. But our programs are open-source. Hence, you cannot apply your principle to your software as better as you can apply it to ours.
This is the Power of open-source.

WinAPI has a serious issue: It doesn't run on anything other than Windows .

I wasn't going to continue this debate, but I am now since I am fed up with this passive aggressive bullshit. Also, I have nothing better to do at the moment.

Just shut up, you don't have to be an ass just because you don't like my oppinion. I treated your oppinion, like an oppinion. Not some type of objective to seek out and destroy. I was trying to be mature, but if you aren't willing then I am not either.

"Fine, then stop using the STL. Stop using the windows.h and program everything yourself. Stop using the compiler, hard code yourself. Stop using your OS, hard code yourself."

Stop doing that, YOU ****ING KNOW WHAT I MEANT, you are just making an invalid point that doesnt even apply to what I was saying.


>you cannot apply your principle to your software as better
I never once said that it was better, try actually reading my post rather that making it up. They all have flaws, they all have overcomings.

I am just saying that if you are running on windows then learning the WinAPI might be worth your while. Then in the long run you

>WinAPI has a serious issue: It doesn't run on anything other than Windows
No shit sherlock, that is why it is called "WinAPI", Not "LinuxUnixMacWinAPI".

I am sorry for my outburst, but I don't like passive aggressive atittudes like the one from the following quote:
>Very Bad advice.
and
>The file you posted is the definition my dear

Thanks very much for all your responses. This really is helpful and has certainly given me an understanding as to where I might find a starting point in this area.

I really do appreciate the help.

Cheers
Danny2000

IMO (= In my opinion) (yea killdude, it's an opinion) you shouldn't use WinAPI for Graphics Programming, it's unportable (as already said by siddhant3s), and there are a lot of better and easier to learn Graphic/GUI Libraries available for cross-platform development, if you write your program, making use of such a library, then you can easily port your application to a wide range of operating systems (And in case of wxWidgets it still uses the OS' native API by default)

killdude>The files were not created by MS, they are created by BloodShed developers, see this code from <windows.h>
Wrong, this file was created by the developers of MinGW, the compiler where the Dev-C++ IDE relies on.

Oh, my bad.

On windows, you don't need anything.
Just use Win32 API (GDI, COM, etc).
You can do everything easily

killdude69, the only way you could hold on to your argument is to talk on situations in which portability has no value. Say, while developing vertical solutions to a non IT based company which uses windows environment, there is no point in providing portability as a feature cause it means nothing to your customer(the customer uses only windows and wouldn't like the distribution of the software to other companies, as in the licence agreement)

In such cases, it is better to exploit tools provided by Microsoft, even if its exactly what Microsoft wants.

In the end its your choice. Be a slave to microsoft or not.

But, I much prefer programs that run on Linux than on windows cause I am a linux lover. Linux is a life saver to people like me who cannot afford to buy windows and who do not want to pirate

And you can't deny the fact that you were wrong when you said that you know the source code of win32 api.

To be ignorant is not a big problem, but not to be able admit mistake and learn from it is a problem.

Cheers