Yes. Icon contains both bitmaps. Thanks, -Koti

This code is off of the top of my head. I have done a few splash screens this way, I know there are other ways to accomplish this, but this has worked for me. class CSplashDlg : public CDialogImpl { private: int m_CurTime; int m_DisplayTime; public: enum { IDD = IDD_ABOUTBOX, SPLASH_TIMER = 100 }; BEGIN_MSG_MAP(CAboutDlg) MESSAGE_HANDLER(WM_INITDIALOG, OnInitDialog) COMMAND_ID_HANDLER(IDOK, OnCloseCmd) COMMAND_ID_HANDLER(IDCANCEL, OnCloseCmd) MESSAGE_HANDLER(WM_TIMER, OnTimer) MESSAGE_HANDLER(WM_DESTROY, OnDestroy) END_MSG_MAP() LRESULT OnInitDialog(UINT /*uMsg*/, WPARAM /*wParam*/, LPARAM /*lParam*/, BOOL& /*bHandled*/) { CenterWindow(GetParent()); m_CurTime = 0; m_DisplayTime = 6; // 6 half-second counts equals 3 seconds before the window disappears. //C: The timer is set for half second resolution. this->SetTimer(SPLASH_TIMER, 500, NULL); return TRUE; } LRESULT OnCloseCmd(WORD /*wNotifyCode*/, WORD wID, HWND /*hWndCtl*/, BOOL& /*bHandled*/) { EndDialog(wID); return 0; } LRESULT OnTimer(UINT /*uMsg*/, WPARAM wParam, LPARAM /*lParam*/, BOOL& /*bHandled*/) { if (SPLASH_TIMER == wParam) { ++m_CurTime; if (m_CurTime > m_DisplayTime) { this->DestroyWindow(); } } return TRUE; } LRESULT OnDestroy(UINT /*uMsg*/, WPARAM wParam, LPARAM /*lParam*/, BOOL& /*bHandled*/) { this->KillTimer(SPLASH_TIMER); return TRUE; } }; Like I said this is off the top of my head, so you may need to fix any compiler errors that I have made. There is probably a better way to destroy the timer that I have created. Create this dialog with a modeless call with something like this: CSplashDlg dlgSplash; dlgSplash.ShowWindow(SW_NORMAL); With the way that it is currently written, it will disappear after 3 seconds. You can change the m_DisplayTime value in order to lengthen or shorten the time that the dialog is displayed. ONe more thing you may want to mess around with the window styles in order to make this dialog top most and whatever else.

Here is a quick link to an MSDN article on writing screen savers in MFC. Might give you a place to start. http://msdn.microsoft.com/library/devprods/vs6/visualc/vcsample/_sample_mfc_saver.htm

That's a property sheet. Each tab is a property page.

Write a property sheet handler (see my shell extension series for a tutorial on doing this). In your IShellPropSheetExt::AddPages() method, you add whatever page(s) you want. The additional registration step is to add your handler under: HKLM\Software\MS\Win\CV\Controls Folder\Display\shellex\PropertySheetHandlers

leave it to the OS? you mean the lovely "This application has performed an illegal operation" message box? ask the average user which is more important: leaking 30 bytes or preventing the app from crashing without warning. if i do a "catch(whatever w)", i always follow it with a catch(...). or, if i'm wrapping C code, or someone else's code, or around code that has the potential to jump out pf array bounds (like when you are filling a buffer that you didn't allocate). in fact, i often put a catch(...) around every major code section, just in case something gets by testing. i also make sure that i do something intelligent in the catch, like attempt to get into a safe state. the headaches that little construct can save are worth megabytes of leaked memory, to the average user. -c

I think I understand what you want to do...try subclassing the dialog listbox controls. First derive a new class for each of the three listboxes from CListBox. CMyListBox1 CMyListBox2 CMyListBox3 Then, in your dialog's main header file (mydlg.h, or whatever) change the default from: CListBox m_ListBox1; CListBox m_ListBox2; CListBox m_ListBox3; to: CMyListBox1 m_ListBox1; CMyListBox2 m_ListBox2; CMyListBox3 m_ListBox3; Don't forget to #include the CMyListBox(x).h files in your code. Then, from your dialog's OnInitDialog function, subclass the controls using this code: VERIFY(m_ListBox1.SubclassDlgItem(IDC_LISTBOX1, this)); VERIFY(m_ListBox2.SubclassDlgItem(IDC_LISTBOX2, this)); VERIFY(m_ListBox3.SubclassDlgItem(IDC_LISTBOX3, this)); Finally, then you can handle the OnSelChange event in your CListBox derived classes. So, you really don't add the function to the dialog class, you make it so you can handle the function from within that class. Good Luck, Frank :)

In registry at [HKEY_LOCAL_MACHINE]\Software\Microsoft\Windows\CurrentVersio\Run\ Add a string value ... Look at the entry that are already exists. Doesn't matter windows version /REMUS

Get WndTabs ( http://www.wndtabs.com ). It does this and more...

Hi, COM object can be stored in the DLL or EXE file. When a COM object is stored in the DLL the only difference with the usual DLL file, is that the COM DLL must have several COM related methods: DllGetClassObject DllRegisterServer DllUnregisterServer DllCanUnloadNow See description of these functions in MSDN for more details... Regards, Alex Gorev, Dundas Software.

Hi, COM object can be stored in the DLL or EXE file. When a COM object is stored in the DLL the only difference with the usual DLL file, is that the COM DLL must have several COM related methods: DllGetClassObject DllRegisterServer DllUnregisterServer DllCanUnloadNow See description of these functions in MSDN for more details... Regards, Alex Gorev, Dundas Software.