Thread: What should be my next step?

Next step, perhaps, is to set out in to the big, wide world. GUI, multi-thread programming, etc.
Considering GUI, you might want to take a pick at some Framework provider such as MFC, GTK, Gnome, etc, and start learning this to make your user interface. This is not an easy thing.
You might not want to mess with threads right away, though, so maybe GUI programming can come first. Good luck. This isn't easy.

Yes, it is. It is mostly because Windows programming, for example, is built around the Windows API which is to say a very poor API. It's purely C, making it mocking, difficult and tiresome to work with.
Add to that that there may be a ton of messages you must handle and handle right or get ill effects that you have no idea to solve, it only makes the situation worse.
Many frameworks (such as VB) handle all this for you, but C++ doesn't. That is why a good GUI Framework is necessary for doing GUI programming in C++.

Is GUI programming in C++ really that hard?

I do not think so, but what little GUI programming I tried in C++ I found tedious. Actually, I found it tedious/boring elsewhere too, even when it comes to creating forms in HTML. The difficult part is probably the design rather than the programming. Threads, on the other hand, are difficult to me, but perhaps I simply have not taken the time to dig in deep into the topic yet.

I haven't done GUI programming for anything other than Windows, though, so I can't speak for other systems.
As for threads, they can be easy, they can be hard. If you spawn a thread to do some work, sure, it's easy. But when you need to start coordinating and synchronizing and updating the GUI at the same time, now it becomes difficult.
Especially since GUI does not like to be updated from multiple threads and that message loops can only be run on the thread that created the window and some API sneer at multiple threads, only favoring the one thread that initialized something, and so on.
It's a difficult world.

The Windows API is not noticeably worse than many other Windowing API's. There are some that are a little bit better than others, but in general, dealing with menus, windows, dialog boxes and such is complex. It makes for a lot of code however you go about doing it. You can HIDE some of that from the programmer (as VB does), and Frameworks will also help dealing with some of the complexity. But as long as the base-API is fairly generic and flexible, then the programming of it will involve a fair bit of code to manage that flexibility.

[I work with embedded graphics system, and it's not majorly different from the Windows API, but it is written in C++ - but it's still a whole heap of code to get a simple window with a few menu-items to show up].

--
Mats

But as long as the base-API is fairly generic and flexible, then the programming of it will involve a fair bit of code to manage that flexibility.

That's true, and I suppose that Joel Spolsky's "law of leaky abstractions" applies to GUI frameworks, so someone serious about GUI programming might have to learn the underlying API anyway.

Originally Posted by laserlight

That's true, and I suppose that Joel Spolsky's "law of leaky abstractions" applies to GUI frameworks, so someone serious about GUI programming might have to learn the underlying API anyway.

Obviously, you can HIDE a lot of the flexibility to make a simple-to-use framework - and if you use C++, you can perhaps also make intermediate and advanced forms of the classes that are more flexible [and thus require a bit more effort].

Making a class that produces a text-based window that has the following structure would make widnows real easy to use:

Code:

class TextWindow: public WindowBase
{
    public:
       virtual void Open(string windowTitle);
       virtual void Close();
       virtual void AddText(int x, int y, string text); 
       virtual string GetText(int x, int y, string text, int len);
       ...     
}

But you'd struggle if you also want to have add graphical elements to that basic class, or use different close/minimize/maximize buttons or some such.

--
Mats