Client/Server Error: BadIDChoice

[wysota]

Where is Qt in that? All I see is C code wrapped into a class. It shouldn't cause any pixmap errors. The problem has to be elsewhere.

[3nc31]

Most Qt code is in the rest of the file....but I don't have any problems with the rest, I have problems when I want to show a new window on startProcess():

waitForChat(portWait, name, &portConnect); //When waitForChat finish, 
// means that other client request for Chat, 
// so the application must show the new window chat.
windowChat = new Chat;
windowChat -> show();

waitForChat(portWait, name, &portConnect); //When waitForChat finish, 
// means that other client request for Chat, 
// so the application must show the new window chat.
windowChat = new Chat;
windowChat -> show();

To copy to clipboard, switch view to plain text mode 

If I commented out this part of the code, the compile error doesn't occur, but I need show a new window...so...

[wysota]

First, these are not compile errors - they are X server runtime warnings that come from incorrect manipulation of X server resources (like widgets).

The problems you experience are caused by the other part of the code even if they are revealed only when you use the code you posted. My very very long shot is that you try to manipulate widgets from within a worker thread, but without seeing the code, I can't say more.

BTW. Using fork() in Qt apps is not a very good idea - it's probably what causes you problems.

[3nc31]

First, Thanks for try to help me ....well, the rest of the code are 8 files (chat.h, chat.cpp, principal.h, principal.cpp, window.h, window.cpp, client.h, client.c) that is the reason for I doesn't post it!...Do I post it?? I think is too much for check!!

[wysota]

No, get rid of those fork() calls. Why do you want to start a separate process for each connection? And why don't you just use Qt networking capabilities instead of using the blocking low-level BSD socket interface? Currently you are doing everything wrong here