|
MFC = Microsoft Foundation Classes. It's a class library with functionality ranging from GUI to linked lists. Probably the most popular toolkit to write Windows applications in. At least it used to be.
ATL = Active Template Library. A class library aimed to ease developing COM applications. Since COM implies ActiveX controls, it's got some limited GUI functionality in it as well. With limited I mean that there are no CListCtrl or CEdit classes.
WTL = Windows Template Library. Is a complement to ATL. Since ATL's GUI support is quite rudamentary - it's enough to cover ActiveX control development, WTL was created to make the development of ordinary Windows apps. WTL builds on the same design principles as ATL, thus WTL code fits like a glove in ATL projects. As it's name implies, it makes heavy use of C++ templates. In my opinion a better mini MFC (MFC has a lot more functionality than ATL/WTL, hence "mini MFC").
CTL = I have no idea. Did you mean STL? STL = Standard Template Library. A standard class and function library, defined in the C++ standard. Contains containers, algorithms, I/O manipulation routines and memory management. Not only is it an excellent library to use, it's also excellently extensible due to its use of templates. Boost[^] is the proof of that.
Since you don't seem to have any idea about these toolkits, I suggest you start at the bottom first, and then work your way up. I'd like to think that STL is a strong foundation of any C++ application, and is thus located at the bottom. Learn it, and you won't have to reinvent the wheel more than twice or thrice.  After that it all kind of depends on what you want to do. ATL is good if you are into COM stuff. But then you'd have to learn COM first. You don't need to know the COM stuff in ATL if you are going to use it in conjunction with WTL though. The windowing code is well separated from the COM stuff.
Whether you should choose WTL over MFC, or vice versa, is mostly a matter of taste. I prefer WTL over MFC because it's not as bloated as MFC, and of its (in my opinion) much better design. MFC may do much more for you than WTL alone, but that's easily cured with STL and Boost (see link above).
--
Weiter, weiter, ins verderben.
Wir müssen leben bis wir sterben.
I blog too now[^]
|
|
|
|
|
I am reading Michael Dunn's WTL for MFC Programmers,he said"Also unlike CWnd when a CWindow object goes out of scope, the associated window is not destroyed...",So I don't understand Why the associated window is not destroyed,PLS show me . Thanks
|
|
|
|
|
|
|
hi
i have embeded an ActiveX control in a web page, when the page is accessed the control downloads and registers successfully on client's machine but it is not shown on the web page, instead a cross icon comes at its place
what might be wrong
plz help me its urgent
regards.
Muhammad Azam
|
|
|
|
|
I have a active-x ATL control. Inside my control I want to use InvalidateRect(), but I can not because it is not a window. Even I do I get Assert letting me know that it failed, because it is not a Window or no handle for the Window. What I am looking that how can I get the handle of the container. In my case it is a dialog Box.
Looking help I found this example. (
ATL Library Reference
CComControl::CreateControlWindow
)
RECT rc = {10,10,210,110};
HWND hwndParent, hwndControl;
// get HWND of control's parent window from IOleInPlaceSite interface
m_spInPlaceSite->GetWindow(&hwndParent);
hwndControl = CreateControlWindow(hwndParent, rc);
Here I am lost. How we can use IOleInPlaceSite to get the Window Handle.
Or if you have any other idea.
Your help will be very much appreciated.
Best regards,
Agha Khan
Agha Khan
|
|
|
|
|
If you're dealing with window less controls, take a look at the IOleInPlaceSiteWindowless interface. Query m_spInPlaceSite for IOleInPlaceSiteWindowless, and use the InvalidateRect() function. Not that I've ever written any window less controls, but from what I can tell, this seems to be the correct way to invalidate rectangles.
--
Weiter, weiter, ins verderben.
Wir müssen leben bis wir sterben.
I blog too now[^]
|
|
|
|
|
Dear Jörgen Sigvardsson:
Well I am NOT writing Windowless control. Perhaps you have noticed that regardless it is Window control or not IOleInPlaceSiteWindowless is implemented. Bottom line is it does not work. I will let you know as soon as creak it.
Thank you for your prompt reply.
Agha Khan
Agha Khan
|
|
|
|
|
BilloKhan wrote:
Well I am NOT writing Windowless control
I don't get it. Didn't you say that the control had no window?
BilloKhan wrote:
Perhaps you have noticed that regardless it is Window control or not IOleInPlaceSiteWindowless is implemented.
Yep. That's because the code can handle both windowed and windowless controls, and it can even configure itself at runtime. IIRC, there's a member variable called m_bWindowless or similar that controls that behavior.
--
Weiter, weiter, ins verderben.
Wir müssen leben bis wir sterben.
I blog too now[^]
|
|
|
|
|
Hello everybody,
I am creating a dll that contains some
Methods and these methods have some styles like:
#define dw_style 1401
After importing my dll and calling that method I want to
Use this dw_style name instead of 1401.
In another word I want a global #define.
////////////For example/////////////////////////////
//In the Dll file
#define dw_style 1401
..
methods
..
////////////////////////////////////////////////////
//////////In the mfc app and after importing the dll
method(dw_style)
..
..
Best Regards
Thanks.
|
|
|
|
|
Export the varible tooo
-----------------------------
"I Think this Will Help"
-----------------------------
Alok Gupta
visit me at http://www.thisisalok.tk
|
|
|
|
|
Define in stdafx.h
What is the problem?
Agha Khan
|
|
|
|
|
I think Me Sollium want to export that in DLL
-----------------------------
"I Think this Will Help"
-----------------------------
Alok Gupta
visit me at http://www.thisisalok.tk
|
|
|
|
|
The answer is also very simple. As we know that define just replaces the actual content what we have defined. It CAN NOT be exported.
Agha Khan
|
|
|
|
|
YEah you are write but what about ENUM in Com DLL.
-----------------------------
"I Think this Will Help"
-----------------------------
Alok Gupta
visit me at http://www.thisisalok.tk
|
|
|
|
|
enum are more like constants whereas #define are macros that get expanded during compilation time.
I hope you will get what I am saying
Have a great day ahead!
Regards,
Sohail Kadiwala
(My Blog - http://blogs.wdevs.com/sohail/[^])
modified 21-Apr-21 21:01pm.
|
|
|
|
|
Sorry Sohail Sir,
i Understand the Difference Between TWO
-----------------------------
"I Think this Will Help"
-----------------------------
Alok Gupta
visit me at http://www.thisisalok.tk
|
|
|
|
|
export them is not suitable. you can define them in the header file.
when you use the dll ,you can include the header file first.
Happy new year!
|
|
|
|
|
Hello everyone
I am creating a DLL using ATL and I want to know
How can I use a timer in my DLL?
Best regards
Thanks.
|
|
|
|
|
you can create Hidden window in your dll that will handle the above cause
-----------------------------
"I Think this Will Help"
-----------------------------
Alok Gupta
visit me at http://www.thisisalok.tk
|
|
|
|
|
I'm developing a multithreaded application mix of MFC & STL stuff using MSVC and having so many DLLs integrated in it .
I have very small question. I want to have little structure(about 3 elements ) associated with each thread and needs to be exported to all DLL in system.
So what's the best way to implement by having simplest old way to have a array of structure/class or have list/map template of structure/class.
Can someone please suggest the best way to go ?
thanks
ben
|
|
|
|
|
It is such a simple question, perhaps I am not following. You may pass any data to any thread even a whole class or more and inside that class cast to that struct or class. By nature all thread functions are static so you have to cast incoming data to desire class.
Agha Khan
|
|
|
|
|
howdy all-
My current problem: I've got this ISAPI DLL, which does some stuff and generates XML. It's written in C++, uses MSXML3, and run's inside DLLHOST...
Oh, and it leaks memory.
(1) Is there a good way to debug this?
(2) If I could convert this to a stand-alone exe, I could attach a debug memory manager.... Can this be done -- can I make an ATL/IIS server extension which is also an exe. (is this what's called an out-of-process server?)
Thanks in advance!
Regards
-peter
P.S. I think I do ask some of the more esoteric questions on this site.... I hope someone has some help or direction for me. Thanks
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br />
Peter Weyzen<br />
Staff Engineer<br />
<A HREF="http://www.santacruznetworks.com">Santa Cruz Networks</A>
|
|
|
|
|
Compile a debug version of your DLL and attach your debugger to DLLHOST.exe. Debug as usual.
|
|
|
|
|
oh...
I wish it were that simple....
But tracking memory leaks is the real problem...
and it's not MFC....
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br />
Peter Weyzen<br />
Staff Engineer<br />
<A HREF="http://www.santacruznetworks.com">Santa Cruz Networks</A>
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
