I am a little rusty now because I haven't done it for a while, because I have mainly been using php in my job, but I have never used wxWidgets before.

I have been programming since 1981 actually started with Sinclair zx basic, then to C on the Amiga, then later C++. I am more a visual person than someone who can read a document and just a understand it. Took me a little time to work out it was because of the space in the folder name. I found that out the hard way, but the problem was solved when I moved the folder from my C: drive to my H: drive. Yes there is a problem with installing to the C: drive. Sometimes it will show you the command and not how to use it, so then I have to search for a code sample to know how to use that command. I do know now that connect is the old way and bind is the new way, but I didn't know that at first. Also going by docs are not always that informative because information changes that is in text too.įor instance on this forum there are people saying to use connect, and then there is bind.

When you see it in a video you know it is going to work because you can see it working. No I haven't got dyxlexia, but I do find some of the docs hard to follow. My point is - NOTHING BEATS AN OFFICIAL DOCUMENTATION!! And thenm when you want to program there - you consult the documentation of GTK/Qt/X11 for the available API. If you want to install Linux - you first stop is the official documentation of the distribution you choose. When you start working with Windows - the first stop absolutely has to be MSDN. ALWAYS FOLLOW AN OFFICIAL DOCUMENTATION!!! My point is - you don't know the needs of this person and you don't know his/her intentions. Or (s)he may make that video just for fun. Reason - it might be working for the person who made the video 10, 15, 20 years ago. As a long time user of wxWidgets I'm sure it is crap.

On the kind of unrelated note - it doesn't matter how good or bad a video you follow is. You program will still need to import functions from those libraries. You use exactly the same libraries in both cases - nothing changes. Third - When you work with C::B all you need is to create a project with appropriate options -selected and it will just work. It is usually recommended to use dyanmic build when you are developing a DLL/plugin yourself in addition to the main binary executable.īuit if your program consist of only 1 main binary - it is preferred to use static build. Second - producing dynamic vs static builds. First of all - why did you use 'CMake'? What is wrong with the provided makefiles?

Codeblocks compiler flags disappeared