Many books teaching C++ still tend to start from C (sometimes even teaching C first) and then adding bits of C++ later on. In my experience, this produces programmers who use the language as an extended C, which in turn leads to bad code and bad designs. There's nothing wrong with C (well, actually...) but the sort of "C with classes" often seen is the worst of both worlds.
"Accelerated C++" teaches C++, and does it very well. It includes many modern (as in post-1998 standard) idioms and best-practices, too, which generally are missing from the various "C++ Primers".
It should be simple to rewrite the implementation to work with normal memory chunks instead of real files - as the downloaded file should be in some kind of byte array, you can emulate the fseek / etc. calls by simply advancing a pointer in this array.
I'm pretty sure I've seen images with little fields for writing text before. I'm wondering how hard that is? Does it take very long to pull off?
I'm an aspiring board game / RPG designer and I want to go completely digital so I'm going to need image files where players can input data. Could you give me some info on this? Maybe tell me where some tutorials are for this sort of thing?
If I was going to pay to get a single page with say 50 different entry slots how much should that cost me?
I have a project that seems to have quite some trouble with MFC. First off, the code base is quite old, the earliest GUI code is from around 1997. It's a MDI GUI with a splitter pane, and in the upper panel, some MFC controls disappear all the time since I switched from VS2003 to VS2008/VS2010. They do not disappear all the time, and it's not always the same controls that disappear. In the worst case, the window can look like this while it's supposed to look like this. Clicking the invisible controls makes the visible again.
Do you have any idea what could be causing this?
Edit: I should also add that "switching" to the tab using a shortcut when you already are on the tab makes the combo boxes visible, but without their border, just the white edit part of the combo box (the dropdown button is also missing).
To make tooltips on controls work, group boxes must have a higher tab value than their content. So all group boxes have a higher tab order in this case.
Are you sure that is that true? It's been a long time since I've dealt with tooltips (in MFC), but I don't remember that restriction. I think the only side effect of having the group boxes be lower in the tab order than their content would be that they could right click on the group box to get "What's This" on whatever the next control in the tab order is. It would be interesting to see if that fixes the disappearing problem, even if it's not satisfactory.
Have you tried programatically bringing the disappearing controls to the front by using SetWindowPos(HWND_TOP, etc.)?
Yes it is true. I have had issues with tooltips not appearing at all, and the solution was to change the tab order. And as said in another reply, removing the boxes alltogether does not fix the problem, either, so changing tab order will not fix it either as well.
I have kind of found a way to fix it now. I'm calling Invalidate() in the page activation code, and it seems to help. Interestingly, before doing so, the combobox that disappeared most didn't disappear anymore when I removed the code in the page activation code that was responsible for filling the combo box - which is weird, it just calls ResetContent and AddString...