No, I think that the main class may pass a reference to itself when it instantiates the other ones (and hopefully needed members are public). 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.

Exactly ! Thanks

You need two SEPARATE objects. The first object constructor initializes the critical section, and its destructor deletes the critical section. It has a member function Lock() and Unlock() The second class, its constructor Enters the critical section of first object, by calling its Lock function. The destructor of this class calls the Unlock() of the first class. That way, you don't have to worry about calling Unlock() explicitly from your code. You also don't have to use a 'global' class from your common code, you use instances of the second class. If you don't want to block out the entire scope of a function, then use the local scoping operators around the second class and the code like so { SecondClass MyLocker; ... code } and it will release when closing brace is met. This is also handy when there is an exception, your critical section is not permanently locked and lost by the unwinding of the exception. Any sufficiently gross incompetence is nearly indistinguishable from malice.

Hi Cédric, I already had a look at your project and even tryed it. The design is great for static data display but unfortunately it lacks real time (dynamic) plotting management features which makes it difficult for me to use as it is. For instance I would need to use the component as a scrolling scope but your component doesn't have the ability to remove and add some samples to the display without having to redraw all samples. This is not acceptable for me because I can have lots of samples and performance is critical. Thanks

are you linking with MFC DLLs? I dont know more about executable created by VC++ 2005 Check with Dependency walker SaRath. _"Where I am from, there is no plan B. So, take advantage of today becuase tomorrow is not promised. - 50 Cent" My Blog | Understanding State Patte_

Another option is to have the function that returns the single instance written this way: CMySingleton* CMySingleton::GetInstance() { static CMySingleton Instance; return &Instance; } This way, everything will be managed automatically and you don't need to take care of releasing the memory. The disandvatage of this version is that you don't have any control over the creation time of the singleton (which is not a problem when you use one but can be problematic when you have a singleton that has a singleton as member for example). Cédric Moonen Software developer Charting control

Yep, that will do it. I would recommend either putting the variable in an anonymous namespace or making your class a singleton though. It's not much of a hack. Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"

Tnarol wrote: Which control or interface would you suggest to use for this to be nice CListCtrl nave

See ShellExecute [^]_** **_ whitesky

You have two compiler errors. The first is a missing argument to GetBuffer(). The second is an erroneous semicolon at the end of PROFILE. "The largest fire starts but with the smallest spark." - David Crow "Judge not by the eye but by the heart." - Native American Proverb

Hi, Wenever you click the treecontrol item the image coresponding to it is retreived from the imagelist and displayed . TreeCtrl sends a notificastion message of type TVN_GETDISPINFO . for this you need to set some flag in the LPARAM in the InsertItem.(check MSDN) So wen the user clicks the item it send a notification and inside you can maintain the list of items thats are geting checked and wen you uncheck you remove the index from your container. You can chcek this link:- http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcesdkr/html/_wcesdk_win32_TVITEM_str.asp[^] Regards, FarPointer Blog:http://farpointer.blogspot.com/