Hi Alton Glad I could help :) Personally, I put it into my InitInstance method or as near to the POE as possible. Doesn't really matter though, as long as it's called before you attempt to embed your object. Tom PS, thanks for the feedback :-D

hi knox, what you said was justified from your point of view i believe. however, you're still young (in the sense that you still have to learn about others), and shouldn't get angry just because you don't understand the OP point of interrest. there are other reason we access to private members avoiding getters/setters/friends that you certainly didn't have in mind when answered. also, don't be so categorical when saying not to use friend accessor. it is very useful in some particuliar case, and Mr. Stroustrup was far from being stupid when he defined this keywork in the C++ language definition... sincerely, TOXCCT >>> GEII power [VisualCalc 3.0  updated ][Flags Beginner's Guide  new! ]

Alton Williams wrote: On debugging what is causing the crashing seems lie with the first call to create for the first "window" Seriously Alton, you have to investigate your own code better than that or no one will ever bother to answer your vague question. It's perfectly allright to have an ActiveX control as a container for another ActiveX control, you don't have to doubt that. The reason why this doesn't work in your code is because you've either removed some important stuff or haven't written the important stuff yet. It's also not very clear what base classes you're subclassing from or why. If you're using MFC to create your controls, the only class you should derive from is COleControl; anything else I would consider highly suspicious and to be removed at once if not given a lot of thought ending with "I've-read-alot-about-it-and-I-know-it's-the-correct-way-to-do-it". ;) I suggest you start over with the CHolderCtrl and create it with the ActiveX control wizard. For every step you take building the functionality of the CHolderCtrl, you should test it with "ActiveX Control Test Container" that ships with MSVC. Don't add the two contained ActiveX controls to CHolderCtrl until the last step. Make sure they can be inserted in an ordinary ActiveX control container before attempting to add them to CHolderCtrl. Alton Williams wrote: Its when I add HolderControl onto other projects I drag and drop it on a diaglogue box and crashes VC++ This feels like the ActiveX control hasn't got all the required interfaces implemented as needed for it to an ActiveX control container. Have a look here[^] for required interfaces depending on what functionality you want to support. Alton Williams wrote: MS Calendar Control 8.0 dosen't behave like this. I has two child ComboBoxes and 50 Statics on it. Now, this sentence really disturbs me since it makes me wonder if you're under the impression that comboboxes, edit and static controls are ActiveX controls. :~ Just to tie up loose ends: com

Alton Williams wrote: void CEditTestCtrl::OnDraw(CDC* pdc, const CRect& rcBounds, const CRect& cInvalid) { DoSuperclassPaint(pdc, rcBounds); //added pdc->FillRect(&rcBounds, &CBrush(TranslateColor(GetBackColor()))); } Use pdc->SetBkMode(TRANSPARENT) to make text background transparent. Nibu thomas Software Developer

Thanks David

try these Api's OpenClipboard :- for Opening Clipboard IsClipboardFormatAvailable :- Checking the requested Data format available. SetClipboardData/GetClipboardData :- For Geting and Setting data into or from Clipboard "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow cheers, Alok Gupta

The easiest way to do this is to simply replace the two .ico files. "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow

Well techincally it would be like this: class A { public: int m_i; float *m_pf; int operator->() const { return m_i; } float& operator*() const { return *m_pf; } }; But - while the * operator makes sense, the -> makes none at all. Why would you want a -> operator to return a basic type? (ie not a pointer to a class) In fact, I belive if you compile the above you will get: warning C4284: return type for 'A::operator ->' is 'int' (ie; not a UDT or reference to a UDT. Will produce errors if applied using infix notation) return type for 'identifier::operator –>' is not a UDT or reference to a UDT. Will produce errors if applied using infix notation The operator–>( ) function must return either a pointer to a class or an object of or a reference to a class for which operator–>( ) is defined. The following example causes this warning: class C { public: int operator->(); // warning }; It is meaningless to apply the member access operator to fundamental data types that have no member access. This warning message will appear when this happens.

But, why is it unavailable? I can't just put a Message_Map in my class that handle the App MenuBar and that will enable the MenuItens? Take a look in my last thread posted: Menu at runtime (dynamic menu) Thanks. Marcos Vinícius

Coordinates in a resource file are specified in dialog base units, while coordinates used in Windows get/move/size APIs are specified in pixels. GetDialogBaseUnits() is one method you can use to convert between the two. /ravi My new year's resolution: 2048 x 1536 Home | Articles | Freeware | Music ravib@ravib.com

You can : CPoint pt(0,0); child->ClientToScreen(&pt); parent->ScreenToClient(&pt); I believe pt will now contain the position of child relative to parent.

Have you set a reflection mapping up (ON_WM_CTLCOLOR_REFLECT) in the class's message map? Steve S

1. Using MFC serialisation mechanisms, you don't. The assumption is made that a single file will contain the entire document. Indeed, use is made of a 'class dictionary' within an MFC archive file, unless you redo the serialisation from scratch. 2. There's a KB article (141921) which covers this nicely. Steve S

Your C++ class must be derived from CObject to be serialisable anyway (see DECLARE_SERIAL, IMPLEMENT_SERIAL). You would put those definitions in your 'base' class's header file, with the implementation, which is normally to call obj.Serialize(CArchive&ar), which you then implement. You can then use these objects in your document's serialize method, using the operators, or alternatively, call the object's serialize method directly. Does that help any? Steve S