John Uhlenbrock wrote: BUT, that would require me getting out of my chair to go get the book You can download a good C++ book. Sonork 100.15206;PavelK

One caveat though. IMAP is not intended to work in download and disconnect mode. You do have to be connected to the server to get maximum use. Outlook and Outlook Express do cache messages and allow disconnected operation (for previously read messages). If you have an always on connection then IMAP is the way to go. Suresh

I know I'm doing something unnecessary here, but it is sunday morning after all... X| float a = 986.366; float \*b = &a; // this prints the bytes representing the float in mem for(int i = 0; i < sizeof(float); ++i ) { printf("%2x", \*((unsigned char\*)b+i)); }

To programatically close the dialog, fake an OK (or Cancel) button-click by doing: PostMessage (WM_COMMAND, IDOK); // fake an OK Post Message (WM_COMMAND, IDCANCEL); // fake a Cancel This should cause your dialog to close as if the user clicked OK. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com

If you mean the Windows Installer, you can use the Registry table with Registry.Name = "-" and Registry.Value = "". Will that do what you want?

I went ahead and posted the code I use to deal with this situation. You can find it at http://www.codeproject.com/useritems/sendcstring.asp

Good stuff - one for the books. Those macros are notorious for introducing 'works in debug but not in release' woes - even without going for ON_CONTROL_RANGE. I noticed that VC7 is much better about catching mismatched fn sigs etc associated with these - actually, its much better at dealing with macros period. Suggest you ferret away a snapshot of the problem as it was, and compile with VC7 when you get a chance. Ain't debugging fun, tho? :)

The constructor gets called first! Try setting a breakpoint there. Brad

I'll agree that Installshield is much to expensive. Anyone from Instalshield out there, PAY ATTENTION!! As for taking hours to learn, that depends on the individual of course. Some master subjects easier than others. In general however just as with it takes time to master it.

i think you are using a CScrollView.. you can use the CScrollview::SetScaleToFitSize(SIZE new_size) All you have to do is to give in the new size of the window for more informations in how to use this.. contact msdn.. or ask me..

Use the api SetWindowText(..)

Create ON_UPDATE_COMMAND_UI handler for the button. Tomasz Sowinski -- http://www.shooltz.com

I have a need for this quite often, and while I haven't gotten around to writing my own class to do it, I know of one that works very well. It's called PassiveDialog and comes with the ITCLib package(http://devcentral.iftech.com). If I look at the code (just to get ideas) I find they've overridden the DoModal function: ... TRY { // create modeless dialog AfxHookWindowCreate(this); if (CreateDlgIndirect(lpDialogTemplate, CWnd::FromHandle(m_hWndParent), hInst)) { if (m_nFlags & WF_CONTINUEMODAL) { m_nFlags |= WF_MODALLOOP; ShowWindow(SW_SHOWNORMAL); UpdateWindow(); Pulse(); } } } ... And created a new Pulse function to pass messages back to the calling code: ... // Check to see if we can do idle work while (bIdle && !::PeekMessage(pMsg, NULL, NULL, NULL, PM_NOREMOVE)) { if (!(dwFlags & MLF_NOIDLEMSG) && m_hWndParent && lIdleCount == 0) { ::SendMessage(m_hWndParent, WM_ENTERIDLE, MSGF_DIALOGBOX, (LPARAM)m_hWnd); } if ((dwFlags & MLF_NOKICKIDLE) || !SendMessage(WM_KICKIDLE, MSGF_DIALOGBOX, lIdleCount++)) { bIdle = FALSE; } } ... For more info, just go download the library. Keep in mind, though, that the code is ©. Hope this helps! -Dave

PostMessage() puts the message in the windows message queue and then returns, no processing of the message is performed before the window's message pump gets to run. With SendMessage() you "forces" the imidiate processing of the message so the message is processed *before* SendMessage() returns. SendMessage() isn't usually a good idea since you can get weird recursive effects if you arn't careful. The most common problem people seem to have with PostMessage() is that they are passing pointers to stack-allocated objects which goes out of scope (are destroyed) before the window procedure gets hold of the pointer... As always, mind your allocations.

How about after the UpdateWindow call in your InitInstance?

Do I understand correctly, you want the last item entered into a list box to be displayed centered vertically? There are no other entries in the list box below this one? If this is what I understand then you can't. What you may have to do is add empty strings to pad the listbox and move the item up.

COM Ports or TCP ports?

Yeah, Frank had the right idea. Because the button is on a dialog bar, you need to enable/disable it like it was a toolbar button. That is, you need to create an Update UI handler for it in your message map: ON_UPDATE_COMMAND_UI(IDC_MY_BUTTON, OnUpdateMyButton) And then in the handler, set the state of the button: void CMyClass::OnUpdateMyButton(CCmdUI* pCmdUI) { if (i_want_the_button_to_be_enabled) pCmdUI->Enable(); else pCmdUI->Disable(); } Hope this helps. ------------------------ Derek Waters derek@lj-oz.com