Check TextNotFound

According to MSDN FindText[^] can search starting from a given character position. Use the chrg and chrgText members of the FINDTEXT[^] structure to set and get the ranges, and lpstrText to set the text to search for. Edit: this is for rich edit home

As long as your code compiles to an exe, you can do it this way: Add the following lines on top of one of your cpp files: #pragma data_seg("shared") LONG g_counter = 0; // This variable is allocated on a page shared between processes... #pragma data_seg() #pragma comment(linker, "/section:shared,rws") Execute the following instruction as soon as possible at startup of your application: InterlockedIncrement(&g_counter); Execute the following instruction immediately before exiting from your application: InterlockedDecrement(&g_counter); When you need the number of instance of your application currently running, use this code: LONG instances = InterlockedExchangeAdd(&g_counter, 0); This method works properly only with exe because they are never relocated while loaded; the trick is to create a section whith the read, write and shared attributes and put there a variable used to count the instances. This way that variable is shared between all the instances of your application, and you can use the Interlocked Variable Access[^] functions to safely access the variable. See also data_seg (C/C++)[^] and /SECTION[^] for more details on how this code works.

why bother?[^] image processing toolkits | batch image processing

visual leak detector[^] -- "Programming is an art that fights back!"

#define new DEBUG_NEW add this line to the beginning of source files witch you suspect leaking memory. then the report will have file name and line numbers. :) (sorry for my poor english.)

Assign unique value for duplicated id, simply. You should assign all unique (different) id for different controls. Only one handler will be called for one id value on MFC message mapping. Because MFC's message mapping is very simple implement which using array of struct, and decide handler by sequential searching. When message map is as below; BEGIN_MESSAGE_MAP(CSampleDlg, CDialog) //{{AFX_MSG_MAP(CSampleDlg) ON_BN_CLICKED(IDC_BUTTON1, OnButton1) ON_BN_CLICKED(IDC_BUTTON2, OnButton2) //}}AFX_MSG_MAP END_MESSAGE_MAP() Compiler recognize as below; (rewriting simply) struct MessageEntry messageEntries[] = { { IDC_BUTTON1, OnButton1 }, { IDC_BUTTON2, OnButton2 } }; If IDC_BUTTON1 and IDC_BUTTON2 are equal, the sequential searching algorithm always find OnButton1 for IDC_BUTTON{1,2}.

There's loads of ways to speed up build time by writing your source code to build fast: - The main one is reduce dependencies between compilation units. Don't include things that you can get away with forward declaring and don't do daft things like have single include files with global lists of error codes - Use interfaces and parameterise from above (PFA) to decouple class implementations from each other - Use PIMPLs to hide implementation details of classes. Don't use protected or private member functions in your base classes - Use DLLs and libraries to help you reduce dependencies and DLLs to reduce link time - (Controversial) Don't use precompiled headers, or if you must only include stuff that's not going to change (standard library headers, third party library headers e.g. boost headers, windows headers). Hiding OS interfaces under portable ones will help speed up your builds as using portable interfaces don't require dragging in loads of OS headers Generally if you're talking less than a second on average to compile each source file and less than 10 seconds for a link there's probably not a lot of reason to try and speed things up more. Another option would be to invest in a newer compiler - VC++2010 has loads of advantages for building over VC6 even if you don't care about the other things like standards compliance and C++0x features. Have a look in "Exceptional C++" by Herb Sutter and "Large Scale C++ Design" by John Lakos for more ideas along these lines. Cheers, Ash

This book answers that question, and many more: Programming Windows with MFC by Jeff Prosise[^] It's time for a new sig. Seriously.

CMenu::GetSubMenu[^] and CMenu::CheckMenuItem[^] might help you with that... > The problem with computers is that they do what you tell them to do and not what you want them to do. < > Sometimes you just have to hate coding to do it well. <

That sound really bad. X| I dont have any clue so dig in the MSDN whether UDP-broadcast are not allowed :confused: Press F1 for help or google it. Greetings from Germany

I would say:"Why don't you post it in the right place?", but you've already done so. Hence I say:"Good luck!". :) If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke [My articles]

To use the in-built system ones (present on XP or later so long as you have a suitable manifest in your executable[^]), then download the latest SDK compatible with VC6[^] and use something like this: // Let's presume your CEdit control is called editControl editControl.SendMessage(EM_SETCUEBANNER, (WPARAM)FALSE, (LPARAM)(L"< enter text here >")); Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

ganesh.dp wrote: help me to solve this one... It could be any number of reasons. Start here. "Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown "Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

No. Not sure. Do not trust a computer... Always check what computer is doing regards, Divyang Mithaiwala Software Engineer

See if this article is of help to you: Shell Tray Info[^] It is a crappy thing, but it's life -^ Carlo Pallini

Iain, Yes this function gives notification based on messagetype. i already tried this... But consider inbox have three 'x' type messages, call the MAPIFindNext function three time with x messagetype. it repeats the same message id and not give other message id. Reason is it's another functionality is, it will give first unread messageid of messagetype 'x'. am i correct? Thanks.

CImage is just a wrapper around a GDI+ Image[^] - you could try using GDI+ - you will need to get a version of the Platform that a) is compatible with VS6, and b) contains GDI+. As this Platform SDK[^] is the last one that works with VS6, I guess it's your best option.