For those new to message boards please try to follow a few simple rules when posting your question.
Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
Keep the subject line brief, but descriptive. eg "File Serialization problem"
Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode HTML tags when pasting" checkbox before pasting anything inside the PRE block, and make sure "Ignore HTML tags in this message" check box is unchecked.
Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
Please do not post links to your question in one forum from another, unrelated forum (such as the lounge). It will be deleted.
Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
No advertising or soliciting.
We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.
I am using a bitmap for a dialog background, which works fine. I am also doing some GDI drawing on top of the bitmap. The problem is updating the GDI drawing causes the bitmap to blink. On a slower computer this may be a major annoyance. The bitmap is loaded in the OnPaint() message handler, where the GDI drawing is also performed and updated. I have tried loading the bitmap image only once, but when the GDI drawing is updated, the bitmap background is erased and not replaced. Is it possible to load the bitmap once, and not have it erased in OnPaint() when the GDI drawing is updated?
Hi everyone, I have worked with basic knowledge of C++. I am struggling to understand how to develop an android app with the Visual C++ platform.I have installed all necessary software yet the sample codes look different from what I have learned. I really need advice, reference sheets or any related stuff that would help me on this path. Thank you.
Hi, I'm still a beginner in coding, I need block cipher source code for my research paper where I need to get the run time for mode of operation, I already find a lot of source code but none of it seems working, example the crypto++ . I don't even know how to set it up. if anyone could help me at least on how to run the crypto++ . and fyi im using a quad core processor laptop, windows 10 and visual studio 2015. :(( :(( :((
If I do some C++ programming and I get to the point where I wish to make some graphical programs, I'm kind of leaning in the direction of using wxWidgets. Was wondering though if there are some books out there that explain things.
I hate to look at code and not know what this word means or this symbol.
For example if I see that something reads:
wxFrame* window = new wxFrame(NULL, -1)
I can't stand not knowing what each part of that means.
So my question is are there any books that do a good job of explaining things like that which I will undoubtedly run into?
I do recognize some of that since I've done some Java which always uses classes so.
If you just got done writing some C++ code and naturally you want to save the file, you tell Windows where you want to save it and then you will see in the bottom field the Save as Type question. If you choose .cpp, and just do that alone the file will not be saved as a C++ source file.
I don't get it.
Seems to me if you tell it that you want to save it as a .cpp source file then all you should have to do is just figure out what you want to name your file and that's all.
But you actually have to give the file the .cpp extension yourself.
I guess you think there is something special about a .cpp file. It is just a text file that (may) happen to contain C++ source code. But that means nothing to Windows, it is just a convenience for us humans.
The file type recognition is controlled by windows and windows by default doesn't know what a .CPP is or many other types for that matter. More distinctly it doesn't know what program to associate to the file type. That is all done via the File Type Association widget in control panel in windows. The save file dialog is a common control dialog from windows and it is it that is directing the prompt.
Usually any good installer for a C++ program makes the changes for association to the file type for you. So either you have a lazy installer for a C++ program or it made the association and you have since broken it.
Whatever the case stop complaining about it and go fix it in the File Type Association widget in the windows control panel. If you need assistance an internet search on "File type association on Windows" should give you a multitude of links to work with. It's a bit like complaining when you click on a .BMP file it doesn't open it in the right editor, yeah so go fix it.
As an extra helpful tip I can tell you that on the file type association it is useful to select plain text filter onto the .CPP file type. That allows windows searches to go inside your .CPP files on a text search. It is sometimes useful if you have a lot of code directories (like I do) to find a specific block of code if you know something unique about it. You can do a computer wide search for the text string in a .CPP file and it has saved me hours of searching.
Please direct me to an article that discusses the difference between a UDP Server application and the Client application.
So far I surmise that the server starts with no knowledge of where a client might be. It can either begin broadcasting data (this is my current need) or listen for a client to connect.
On the other hand, the client must know the address of the server and it either begins listening for broadcasts from the server or it sends a message to the server to accomplish something, such as to solicit some information from the server.
I have done that. Here is the first page of results from my good search for “udp sockets”
Before providing the list, I do suspect that if I already knew the differences I may well find that information in these sites. As I do not, that information can be rather difficult to pick out.
https://www.cs.rutgers.edu/~pxk/417/notes/sockets/udp.html goes right to code, does not discuss the difference http://www.cs.dartmouth.edu/~campbell/cs60/socketprogramming.html does not discuss why there is client and server with UDP https://en.wikipedia.org/wiki/Network_socket does not discuss https://www.w3.org/TR/tcp-udp-sockets/ Section 9 begins UDP, jumps right into code with no explanation Just for the record, this is the most thorough discussion I have found http://www.binarytides.com/programming-udp-sockets-c-linux/ does not discuss the differences https://www.abc.se/~m6695/udp.html does not discuss https://developer.chrome.com/apps/sockets_udp does not discuss https://cs.nyu.edu/~bacon/phd-thesis/diss/node32.html does not discuss the differences https://wiki.python.org/moin/UdpCommunication “server” is in the article in only one place discussing a Windows bug http://www.microhowto.info/howto/listen_for_and_receive_udp_datagrams_in_c.html Starts off with: Suppose that you wish to write a server that implements the … But does not address the differences. References RFC 867 which does not discuss the differences
Do I need to continue? I am looking for a discussion on the differences between server and client in UDP operations. Not in the code difference but in the difference in concept between the two. Looks to me like two servers or two clients can well carry on a conversation via UDP packets.