C / C++ / MFC

29-Sep-01 0:45

Hello,

Does anyone one know what should be set in the PreCreateWindow function to remove the frame border from the CChildFrame window and\or the CFormView derived class?

I want to have something that looks more like a VB Form / Dialog window in that I would prefer a rasied 3d edge rather than the frame.

I think you have to do something with the cs.style, but cannot seem to get it right.

I thought something like :

BOOL CChildFrame::PreCreateWindow(CREATESTRUCT& cs)
{
	cs.style &= ~WS_THICKFRAME;

	if( !CMDIChildWnd::PreCreateWindow(cs) )
		return FALSE;

	return TRUE;
}

Any suggestions would be welcome.

Thanks.

Giles

Paolo Messina29-Sep-01 2:37

29-Sep-01 2:37

And if you add WS_DLGFRAME ?

cs.style &= ~WS_THICKFRAME;
cs.style |= WS_DLGFRAME;

Paolo

------
"airplane is cool, but space shuttle is even better" (J. Kaczorowski)

Giles29-Sep-01 2:59

29-Sep-01 2:59

I have tried this. It does remove the thich frame, and replace it with a thin frame, about have the thickness.

I still cannot get the edge of the MDI window to be just rasied rather than a frame.

The CFormView has no border in the resource editor.

Any ideas?

Thanks,

Giles

Paolo Messina29-Sep-01 3:05

29-Sep-01 3:05

Oh, I understand now what you want to get! Smile | :)

You can't do anything from the dialog editor, because the CFormView is child of your CChildFrame window. I had a demo project that turned a from into a dialog, but I can't find it anymore.
However, try removing WS_EX_CLIENTEDGE from the extended style of the frame window.

Paolo

------
"airplane is cool, but space shuttle is even better" (J. Kaczorowski)

Giles29-Sep-01 3:13

29-Sep-01 3:13

I tried both

cs.style &= ~WS_THICKFRAME;
cs.style |= WS_DLGFRAME;

cs.dwExStyle &= ~WS_EX_CLIENTEDGE;

and just

cs.dwExStyle &= ~WS_EX_CLIENTEDGE;

by itself, but no luck.

I'm sure it must be simple, but it feels like I've been though all the permutations.

Giles

Paolo Messina29-Sep-01 3:58

29-Sep-01 3:58

Yes, it doesn't work because of:

BOOL CFrameWnd::PreCreateWindow(CREATESTRUCT& cs)
{
	if (cs.lpszClass == NULL)
	{
		VERIFY(AfxDeferRegisterClass(AFX_WNDFRAMEORVIEW_REG));
		cs.lpszClass = _afxWndFrameOrView;  // COLOR_WINDOW background
	}

	if ((cs.style & FWS_ADDTOTITLE) && afxData.bWin4)
		cs.style |= FWS_PREFIXTITLE;

	if (afxData.bWin4)
		cs.dwExStyle |= WS_EX_CLIENTEDGE;

	return TRUE;
}

Try to do that in OnCreate(), using ModifyStyle().

Paolo

------
"airplane is cool, but space shuttle is even better" (J. Kaczorowski)

Giles29-Sep-01 4:38

29-Sep-01 4:38

Still no luck. The frame border is still there. I wanted to use this for a database app, which I am converting from Access. I wanted something that had a forms like in Access with no frame.

If you do see an example of this in the future I would be grateful if you could tell me how?

Thanks once again,

Giles

Paolo Messina29-Sep-01 4:46

29-Sep-01 4:46

It was the view...

void CDemoView::OnInitialUpdate()
{
	ModifyStyleEx(WS_EX_CLIENTEDGE, 0);
	//..
}

Paolo

------
"airplane is cool, but space shuttle is even better" (J. Kaczorowski)

Re: correction

Paolo Messina29-Sep-01 4:54

29-Sep-01 4:54

The correct way:

CMyView::OnInitialUpdate()
{
	ModifyStyleEx(WS_EX_CLIENTEDGE, 0, SWP_FRAMECHANGED);
	CFormView::OnInitialUpdate();
	// the rest
}

Paolo

------
"airplane is cool, but space shuttle is even better" (J. Kaczorowski)

Re: correction

Giles29-Sep-01 5:08

29-Sep-01 5:08

Great!!!!!! Big Grin | :-D

Your a genius.

Thanks for all your help!

Giles

Paolo Messina29-Sep-01 5:39

29-Sep-01 5:39

I'm only hard-headed ...
I already did that once, so I should be able to do it again Wink | ;)

Paolo

------
"airplane is cool, but space shuttle is even better" (J. Kaczorowski)

Nish Nishant6-Mar-02 9:11

Nish Nishant

6-Mar-02 9:11

Brilliant Paolo!

Nish

[Signature temporarily down]

Paolo Messina6-Mar-02 9:36

6-Mar-02 9:36

For the whole thread, or just the last sentence? Smile | :)

However, thanks!
Paolo

------
"airplane is cool, but space shuttle is even better" (J. Kaczorowski)

winsock server accepting multiple clients, sending data back to all clients

Nish Nishant6-Mar-02 9:43

Nish Nishant

6-Mar-02 9:43

Paolo Messina wrote:
For the whole thread

Yes. More than the solution, it was your approach which I thought was amazing! Slowly moving towards the goal.

Joaquin had posted this link in one of his posts today [Mar 7th 2002]. That's why I actually replied to a thread that's almost half an year old Smile | :)

Nish

[Signature temporarily down]

Kuniva29-Sep-01 0:25

Kuniva

29-Sep-01 0:25

hi, ok first of all, this project is pure win32, no MFC involved. I'm making a server that can accept multiple clients, when a client sends some data, the server sends it back to all connections. I'm using the sockets in asynchronous mode, i've already made the client but i'm having problems with the server and i've been trying to firgure it out for so long, i thought i'd try here. I can't find any example on the net of this, and i'm starting to believe there isn't one, all i could find was a server that used threads and echoed the data back to the connection the data was sent from.

This is what i have so far:

First i create a socket that listens for incoming connections, this socket is called "sd". then i have an array of 50 sockets: ac[50]
i initialize all these sockets with a loop from one to 50 giving them the value "NULL"

This is the code that is executed when the listening socket posts the FD_ACCEPT message to accept any incoming connection:

case FD_ACCEPT:
sockaddr_in sinRemote;
nAddrSize = sizeof(sinRemote);
ac[conn] = accept(sd, (sockaddr*)&sinRemote, &nAddrSize);
MessageBox (NULL, "Accepted incoming connection." , "Accepted", 0 + MB_ICONASTERISK);
conn = conn + 1;
break;

This works fine and multiple connections are accepted. The conn integer keeps up with the number of connections established.

Now here's the problem: every incoming connection is accepted by the ac socket, the first one by ac[0], the second one by ac[1] and so on and so on... till 50.
I used WSAAsyncselect on all ac sockets from 0 to 50 so when they are ready to receive data they post a message. Now what is supposed to happen is that somehow the received data is sent back to all connections, here's what i have now:

case FD_READ:
c = 0;
do
{
bytes_read = recv(ac[c], buf, sizeof(buf),0);
buf[bytes_read] = NULL;
c = c + 1;
}
while(bytes_read<=0);

for (y=0;y<=50;y++)
{
if (ac[y]!=NULL)
{
Len = strlen(buf);
if (send(ac[y], buf, Len, 0) == SOCKET_ERROR)
{
MessageBox (NULL, "error echoing data" , "Error", 0 + MB_ICONHAND);
}
}
}
break;

I tried to make multiple telnet connections and it worked but when i sent something, it got echo'd for the first connection but then it gave me the "error echoing data" messagebox...

Can anyone please tell me how to handle FD_READ so the server sends the data back to all connected clients???

Thanks... Dead | X|

Kuniva

P.S.: this thing is really startin ta bug me

Re: winsock server accepting multiple clients, sending data back to all clients

29-Sep-01 2:44

Maybe more things are wrong in your code, but take a look at that:

case FD_READ:
c = 0;
do
{
bytes_read = recv(ac[c], buf, sizeof(buf),0);
buf[bytes_read] = NULL;
c = c + 1;
}
while(bytes_read<=0);

Since the sockets are asynchronous, there is a good chance that recv(..) will return SOCKET_ERROR for most of the sockets (the ones in which there is no pending data). SOCKET_ERROR equals to -1. Which means that your
buf[bytes_read] = NULL;
statement will overwrite some memory... In debug build there are good chances you won't even notice it - but there is a good chance that in Release build the program will crash.

That would probably also damage the results of your
Len = strlen(buf)
line.

Anyway, whenever you get a SOCKET_ERROR result, check the value returned from WSAGetLastError(). If this value equals WSAEWOULDBLOCK then it means the operation will complete later. I recommend reading Windows Sockets Network Programming by Bob Quinn (I think he's the Charles Petzold of Winsock) and Dave Shute, ISBN 0-201-63372-8.

Another note - writing a server that relies on Windows messages (or event Events) is ok for a small-scale server. But in a large one that should handle thousands, and probably even hundreds of simultaneous connections, you'd probably use some other method (like IOCP).

Good luck!

Shell API

vijayaramaraju28-Sep-01 23:47

vijayaramaraju

28-Sep-01 23:47

Hi, I've to invoke an application whose path is not known. I am required to search for it in the application path instead of opening the CFileDialog can you help me how to do it

Re: Shell API

Paolo Messina29-Sep-01 0:17