In the output screen, top right hand corner of a windows application, there is the red standard close(x) button. In my application I need to get rid of it. How can that be done? Hopefully someone can tell me how to do that.
In the output screen, top right hand corner of a windows application, there is the red standard close(x) button. In my application I need to get rid of it. How can that be done? Hopefully someone can tell me how to do that.
You could try this:
Code:EnableMenuItem(GetSystemMenu(hwnd, FALSE), SC_CLOSE, MF_BYCOMMAND | MF_DISABLED);
All truths are half-truths. - A.N. Whitehead
Re your code to get rid of the close(x) button: the compiler doesn't like it. No reason given. (My CodeBlocs doesn't give reasons.) Bur thank you anyway.
> the compiler doesn't like it. No reason given. (My CodeBlocs doesn't give reasons.)
This is BS
The build log and/or build messages tabs at the bottom are sure to show something.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
You don't know what a window handle (hwnd) is?
Looks like you need to learn the basics of programming Windows.
All truths are half-truths. - A.N. Whitehead
It looks like you are a pathetic little loser who wants someone else to write the program for them. Get lost.
All truths are half-truths. - A.N. Whitehead
A forum is there to help others who are less proficient / who know less. Responding to a perfectly decent request for help, by telling the other person he is a looser, because he doesn't know something, shows what you are using this forum for. Namely to create opportunities to wank your ego.
Then start by posting actionable information, not random one liner "it doesn't work", and lots of whining about how people are not helping you.
To date, you've posted ZERO code and ONE error message.
Instead of bleating "My CodeBlocs doesn't give reasons", you should have done your own STFW for "code blocks doesn't show error messages".
1. If you don't see the log panel at the bottom, press F2
2. If you don't see the build/error logs, then right-click and choose toggle...
3. Choose the views you want to see
4. When you've got the logs, then copy them to the clipboard for pasting to your helpers.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
I always found the pursuit of knowledge to be a pride swallowing experience, especially when you seek knowledge on public forums. I always have to remind myself that I'm seeking the expertise of someone else.. i.e. I'm expecting someone(usually someone with more knowledge) to use their time and energies to help me.