This is an excellent article explaining all the nuts and bolts of MFC's command routing. http://www.microsoft.com/msj/0795/dilascia/dilascia.aspx[^] There will be an exam to make sure you've read it before you're allowed to have any more biscuits. Ever. Once you've read it, the following will make sense: I think you need to add an OnCmdMsg handler to your View class, to give the temporary edit box a quick bite at the cherry. Alternatively, use the CMyView::OnEditCopy handler to send a WM_COPY message to your edit box, if it exists. (and same for paste, cut...) Good luck, Iain. In the process of moving to Sweden for love (awwww). If you're in Scandinavia and want an MVP on the payroll (or happy with a remote worker), give me a job!

See How to: Configure Visual C++ Projects to Target 64-Bit Platforms[^]. Of one Essence is the human race thus has Creation put the base One Limb impacted is sufficient For all Others to feel the Mace (Saadi )

Thanks superman.. I always use documentation. but in this case I totally forgot it. :)

The blinking cursor is called a Caret and can be created using the CreateCaret function and shown using the ShowCaret function. «_Superman_»

I solved the problem. There was a resource leak in my code, but it was crashing in MS VC++ code. I was getting the handle to dc(GetDC()) in some UI update event(ON_UPDATE_COMMAND_UI), but I was not releasing it.

But I added a new dialog, placed a picture control on it and loaded a bmp. It works fine in unicode also. I think it should not be specific to property sheets. what do you say ?

:) - ns ami -

:-D 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]

Its working. now I change the directory permissions just before calling save.

ThisIsMeRon wrote: I have application in which I need to show a progress window frm a worker thread. Not a good idea. The UI component should be owned by the primary thread. The secondary (i.e., worker) thread should post messages to the primary thread indicating the progress. It's all explained in more detail here. "Love people and use things, not love things and use people." - Unknown "The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch

There shouldn't be a CBitmap::Save call....it should be a Gdiplus::Bitmap::Save call. Mark Salsbery Microsoft MVP - Visual C++ :java:

Thanks dude.

I had the same problem when porting from VS2005 to VS2008. I avoided it using dynamic allocation something like this: std::vector *v; v = new ???; v->push_back(***) This works in both debug and release mode :) ^^

I had the same problem when porting from VS2005 to VS2008. I avoided it using dynamic allocation something like this: std::vector<???> *v; v = new ???; v->push_back(***) This works in both debug and release mode :) ^^

This is still at start:) I have this idea.. I will draw the text "Type Title Here" at the top of doc. When user clicks on this text I will show a rectangle surrounding the text and a cursor at that position. User types the title, I'll accept the input character by character and display it. As soon as the user clicks outside the rectangle I will hide the rectangle. Should I go on with this? or Have a better idea? Please suggest. Thanks Ron

yo buddy.. that will surely help. :-D Thanks!

thanks for your suggestions. Let me give you broader view of what Im trying to do.. Im developing an application that needs to send xml files to a mac system. A similar app on mac should be able to open and interpret the files. Now the xml file has a header and a data parts. The Data part will contain multiple node hierarchies as the one that follows: <item> <id> 123 </id> .... .... <note> some notes</note> <image> <bitmap> <height></height> <width> </width> ... </bitmap> </image> </item> So I can use zlib on such multipe xml files. what say.. Please suggest.

:) Welcome... Don't forget to call DeleteObject to delete it when it is no longer needed. - NS - [ODBaseBtn]