Thanks Madhu.

RVA – Relative Virtual Address represents a relative address within a file on the disk. When dll is loaded adding this RVA address to base address gives us the actual address of a function in memory. You need to google first, if you have "It's urgent please" mentioned in your question. ;-)_AnShUmAn_

Ahmed Charfeddine wrote: I need to understand, if possible, why actually there is a macro arround __declspec(dllexport), such that it can be translated into a dllexport or dllimport... Such macros are usually written to avoid typing __declspec(dllexport) every time. Something like MYEXPORT would do instead. Also, the same macro would be defined as __declspec(dllimport) in the importing side, so I can be just double lazy. :) There are several good articles at CP on the DLLs section[^], I recommend you read them. It is a crappy thing, but it's life -^ Carlo Pallini

If the toaster contains a camera, that is OK, but I am not interested in those pictures. I want it to be smart enough to deliver on its promises all by itself. That is what embedded systems are supposed to do, not bother me, just deliver the results. Now if the manufacturer needs an interface to service the device, he can do so; but again, I'm not interested in it. Oh wait, I might want to include it in my next domotica infrastructure. Have to rethink. If so, it won't be a serial port I'm afraid. :) Luc Pattyn [Forum Guidelines] [My Articles] - before you ask a question here, search CodeProject, then Google - the quality and detail of your question reflects on the effectiveness of the help you are likely to get - use the code block button (PRE tags) to preserve formatting when showing multi-line code snippets

Ummm - why not just change your custom view to derive from CRichEditView? You'll also have to replace CView with CRichEditView in various places in your view's .cpp file, for example, in an IMPLEMENT_DYNCREATE statement, a BEGIN_MESSAGE_MAP statement and where CView methods are called (e.g. your view's PreCreateWindow method will call CView::PreCreateWindow - that should be changed to CRichEditView::PreCreateWindow). Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p

You need to inform the main frame (or something) that the state of that command button has changed - maybe this page[^] can help? You should probably not change the image list directly, instead send a message to the main frame telling it about the state change. Then it can manage the change to its UI.

Thanks That problem is solved with the follosing code. hIcon = AfxGetApp()->LoadIcon(IDI_ICON1); m_wndToolBar.GetToolBarCtrl().GetImageList()->Replace(8,hIcon);

Hi, You can set cold and hot images for the toolbar. This is the sample code. CImageList img; img.Create(IDB_HOTTOOLBARS, 22, 0, RGB(128, 128, 128)); m_wndToolBars.GetToolBarCtrl().SetHotImageList(&img); img.Detach(); img.Create(IDB_COLDTOOLBAR, 22, 0, RGB(255, 255, 255)); m_wndToolBars.GetToolBarCtrl().SetImageList(&img); img.Detach(); Here m_wndToolBars is the CToolBar object.And IDB_HOTTOOLBARS and IDB_COLDTOOLBAR are the Bitmap imges in the resourse editor. Regards Arun