C / C++ / MFC

I think it's the same cookie under a different name. "Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

void UpdateGame() { MessageBox(hWnd, "Doing the update", "Game", MB_OK); } :laugh: :laugh:

Yes, pretty much similar code. ..and the idea of "variable count ", I will eventually have a file where I will keep the data and will add to it as required - sort of database . I messed up a little and had the main loop in the array... It has been great "discussion" and it helped a lot... Thanks PS I may post the final version ,if anybody cares. Right now it is lot of "cut and paste" to put it in code which actuality does puts menu /submenu into main code.

The issue was /is the relations between QMenu and QAction...I did solved this by looking at many similar examples. But as told many times - posting it here was my mistake, lesson learn. Thanks.

It takes all kinds. :sigh: "the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle

Colour me not impressed! As long as you take the free option, I guess you didn't loose much, except maybe some time. Also there is the question of getting bad programming habits, but those can be fixed over time. These days there are many free online course from very reputable sources like MIT OpenCourseWare | Free Online Course Materials[^]. You might want to take a look at some of them. Mircea

In Windows, there are additional, O/S-level exceptions, that provide this sort of information. Look for "Structured Exception Handling". If you use MSVC, you may use the _set_se_handler function in main() and in the main function of each thread to convert Structured Exceptions to C++ exceptions. There may be similar O/S- and compiler-specific methods in other environments. Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.

One more detail - on Windows, you must open the file in "binary" mode using the O_BINARY flag (for open) or "rb" (for fopen). Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.

mike7411 wrote: Can someone help me understand how this line works: the statement: if (!file) means if the variable file equals null then ... But you have already instantiated file with the line: ifstream file; So it is very unlikely that file will be null. The open method sets the failbit status if the open fails, and that is what you need to test. If you use STL classes then you must follow the STL rules, not the old C-style ones. See std::basic_ifstream<CharT,Traits>::open - cppreference.com[^] for full details.

First things first, you're ignoring the return value of _setmode. If it's -1, the call failed, but you'll never know. Second, after reading the documentation on _setmode and associated error links, it appears you cannot use cout with the mode of stdout switched to Unicode. You have to use wprintf instead: #include #include #include using namespace std; int main() { int r; r =\_setmode(\_fileno(stdout), \_O\_U16TEXT); if (r == -1) perror("Cannot set mode"); wprintf(L"\\u0394\\u03AD\\u03BB\\u03C4\\u03B1\\n"); return 0; } CORRECTION: You CAN use COUT, but you must use the wide version of it, but note the L in front of the string being output. It MUST be there: #include #include #include using namespace std; int main() { int r; r =\_setmode(\_fileno(stdout), \_O\_U16TEXT); if (r == -1) perror("Cannot set mode"); wcout << L"\\u0394\\u03AD\\u03BB\\u03C4\\u03B1" << endl; return 0; } Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak

jschell wrote: if Stroustrop is the name then I would consider that better. Agreed. :) "the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle

As you guessed, erase invalidates all iterators on the container. Your problem is known as the Erase–remove idiom[^] There are different ways of solving it: 1. The "manual" way: auto pos = myVector.begin(); size_t i=0; while (pos != myVector.end()) { if (*pos ==3) { myVector.erase(pos); pos = myVector.begin() + i; } else { ++i; ++pos; } } 2. The "semi-automatic" way: auto pos = myVector.begin(); while (pos != myVector.end()) { if (*pos ==3) pos = myVector.erase(pos); //erase returns an iterator pointing to next element else ++pos; } 3. The "old fully automatic way": myVector.erase(std::remove(myVector.begin(), myVector.end(), 3), myVector.end()); 4. The "new fully automatic way" (since C++20): std::erase (myVector, 3); Disclaimer: I didn't compile any of the code above; some errors may/will exist :) Mircea

If you want things run in order then do not use async. See the example at std::async - cppreference.com[^].

While you are absolutely right, I don't know of any heap manager that behaves the way you describe. Let's say that calling delete on an int array is a smaller sin, a "peccadillo" that will place you on one of the first circles of hell. :laugh: Mircea

My best practice doesn't fit either of your suggestions... If I am creating a new database layer (which I have numerous times) then the caller would never provide the SQL. If the business layer(s) need new database logic then the database layer should be modified to provide it. The caller provides the parameters that would be used in the call. Then within that database layer method it would decide how to process the parameters and SQL (provided by the method.) So it looks like the following. void DatabaseDoX(param1, param2,...) { // multiple variations possible std::string fullyFormedQuery = sprintf (SQL_X, param1, param2, ... ); There are quite a few variations on the above. For example consider the complication of a user initiated call where they might specify different 'query' terms (like data range, customer name, etc) But all still hide the SQL. Certainly there are design considerations for example your code might be coming from within the database layer (not a business call at all.) If so then I suspect that usage would actually vary depending on what the database layer was specifically doing in the code path.

mike7411 wrote: I got it from MIT's OpenCourseware. I see the MIT is still at the cutting edge of technology !! :rolleyes: CI/CD = Continuous Impediment/Continuous Despair

See, for instance Array Decay In C - GeeksforGeeks[^]. "In testa che avete, Signor di Ceprano?" -- Rigoletto

Thanks for your responses. I wish I had a line to Mark Russinovich. I'm sure he would know. The difficult we do right away... ...the impossible takes slightly longer.

I do appreciate your comments, especially about QT. However, since my comments are not received well...let sleeping dogs sleep.. Have a swell day.

Just to be clear, I'm done with this. Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles. Dave Kreskowiak