ATL / WTL / STL

The problem with classCDateTimePickerCtrl

8-Sep-03 20:33

I thought the interface template IPersistStreamInitImpl had implemented the persistence. I overwirite the load and save methods, it is OK now!
Thanks a lot!

Foxray7-Sep-03 14:42

7-Sep-03 14:42

When used dynamicaly in a composite ActiveX control, the member funcion "create" of CDateTimePickerCtrl failed (the HWND returned is NULL).
Any advice will be appreciated, and Thak you in advance!

Michael Dunn7-Sep-03 19:23

Michael Dunn

7-Sep-03 19:23

Did you call InitCommonControls()?

--Mike--
Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber
Ericahist updated (again) Sep 6!

Foxray7-Sep-03 20:49

7-Sep-03 20:49

I have called InitCommonControls(), but create failed yet, do you have other advice,
thank you anyway!

Braulio Dez8-Sep-03 21:42

Braulio Dez

8-Sep-03 21:42

Hi,

I had the same problem with the "cool" control ( comboBoxEx and DateTimePicker), I solve it in this way:

// ----
// Trying to register Combo box Ex
INITCOMMONCONTROLSEX iccex = { sizeof(INITCOMMONCONTROLSEX), ICC_USEREX_CLASSES };
InitCommonControlsEx(&iccex);
InitCommonControls(); // Obsolete remove if not necessary
// ----

It seems that InitCommonControlsEx works better Smile | :)

HTH
Braulio

Foxray10-Sep-03 23:17

Please Help: ATL Embedded and Shell Extension Question.

10-Sep-03 23:17

Except do as you say, I have to copy the comctrl32.dll to the working derectory, Smile | :)

Thank you anyway!

LittleCoder5-Sep-03 12:17

LittleCoder

5-Sep-03 12:17

Hi everyone,
First, I'd like to say that I'm new to both ATL and Shell Extension programming, and I'm running into a brick wall the last three day. I would like to ask for your expertise of the topic.
Currently, I'm working on a UI design of an ATL project. On one the UI, I have an embedded Window Explorer. Thanks a little trick from Matthijs Hollemans's Windows Explorer wildcard selection shell extension article, I was able to get the hold of the right-hand side window, which is a list view, of the embedded explorer. However, when I try to used the API function SHGetPathFromIDList trying to get the path of the list view item pidl (i.e: item.LPARAM), it always returns that path to the desktop. For example, if the selected file is C:\Test.txt, the API function would return C:\Documents and Settings\CurrentUserID\Desktop\Test.txt. It doesn't matter what directory you navigate to, the returned path is always the desktop. Two questions raised for me:

1. Is there a way to just query for the directory path of the embedded window explorer?
2. How and what are the steps do I need to take to resolved the extension issues in this specific scenario?

Thanks so much for your help

Here is the class I used to create the embedded Window Explorer
class CDirFileView : public CWindowImpl<cdirfileview, caxwindow="">
{
public:
DECLARE_WND_SUPERCLASS(NULL, CAxWindow::GetWndClassName())
BOOL PreTranslateMessage(MSG* pMsg)
{
if((pMsg->message < WM_KEYFIRST || pMsg->message > WM_KEYLAST) &&
(pMsg->message < WM_MOUSEFIRST || pMsg->message > WM_MOUSELAST))
return FALSE;
// give HTML page a chance to translate this message
return (BOOL)SendMessage(WM_FORWARDMSG, 0, (LPARAM)pMsg);
}

BEGIN_MSG_MAP(CDirFileView)
END_MSG_MAP()

// Handler prototypes (uncomment arguments if needed):
// LRESULT MessageHandler(UINT /*uMsg*/, WPARAM /*wParam*/, LPARAM /*lParam*/, BOOL& /*bHandled*/)
// LRESULT CommandHandler(WORD /*wNotifyCode*/, WORD /*wID*/, HWND /*hWndCtl*/, BOOL& /*bHandled*/)
// LRESULT NotifyHandler(int /*idCtrl*/, LPNMHDR /*pnmh*/, BOOL& /*bHandled*/)

BOOL DestroyWindow()
{
return CWindowImpl<cdirfileview, caxwindow="">::DestroyWindow();
}

};

Linker error using MFC and STL

Jambolo3-Sep-03 18:53

Jambolo

3-Sep-03 18:53

I have a non-MFC project using std::string that is compiled into a library (Confetti.lib). My main project is an MFC project that uses this library. I get the following linker errors:

msvcprtd.lib(MSVCP70D.dll) : error LNK2005: "public: __thiscall std::basic_string<char,...>::~basic_string<char,...>(void)" (??1?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@XZ) already defined in Confetti.lib(ParticleSystem.obj)
msvcprtd.lib(MSVCP70D.dll) : error LNK2005: "public: __thiscall std::basic_string<char,...>::basic_string<char,...>(char const *)" (??0?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@QAE@PBD@Z) already defined in Confetti.lib(ParticleSystem.obj)

Can anyone tell me why this is happening and how to fix it?

Also, if I ignore msvcprtd.lib, then I get lots of dll import/export errors for std::basic_string.

Re: Linker error using MFC and STL

Steve S3-Sep-03 21:45

Steve S

3-Sep-03 21:45

What's your code generation for both? Multithreaded, singlethreaded, dll, etc?

Steve S

Re: Linker error using MFC and STL

Jambolo4-Sep-03 1:09

Jambolo

4-Sep-03 1:09

Both are multithreaded.

However, I found that linking with the MFC DLL causes linker errors, and linking statically does not. My guess is that for some weird reason (a bug?), the MFC DLLs export some STL symbols.

WTL DDX with controls, really?

Ernesto D.3-Sep-03 15:39

Ernesto D.

3-Sep-03 15:39

I just dont get it, WTL´s DDX facilities define a DDX_CONTROL() macro that take an ID for a control, and an object to attach it to.
However, if i do something like this:

BEGIN_DDX_MAP(CMyDlg)
DDX_CONTROL(IDC_MYEDIT, m_cEdit)
END_DDX_MAP()

where IDC_MYEDIT is (of course) and edit box on my dialog, and m_cEdit is a member variable of type CEdit, then this class wont complie! because SubClassWindow() (witch is called by ddx), is NOT a member of CEdit!, i suppose i could write a class derived from CWindowImpl<derivedclass, cedit=""> and pass objects of it to DDX_CONTROL(), but i assumed that the whole purpuse of DDX was to make mi life easyer not harder!, it would be FAR more trouble to write a class for EVERY type of control i want to use DDX with, than just create control class member variables on my dialog, and just Attach() them to the "physical" controls on the dialog, early on my OnInitDialog() function!
Im i missing something???
what is the purpuse of DDX_CONTROL() if it CANT be used "normally" with controls?

Michael Dunn3-Sep-03 15:52

Michael Dunn

3-Sep-03 15:52

DDX_CONTROL requires a class with a message map, that is, a CWindowImpl-derived class. The control wrappers are all CWindow-derived, so they can't be used with DDX. You need to do something like:

class CEditImpl : public CWindowImpl<CEditImpl, CEdit>
{ public: DECLARE_EMPTY_MSG_MAP() };

and use CEditImpl for your m_cEdit variable. Yes, it's a hassle. Frown | :(

--Mike--
Ericahist | Homepage | RightClick-Encrypt | 1ClickPicGrabber
Ericahist updated Aug 30!

Li Lirong3-Sep-03 16:32

Li Lirong

3-Sep-03 16:32

You can try CContainedWindowT<cedit>.

Regards,
Lirong

Ernesto D.3-Sep-03 17:55

Ernesto D.

3-Sep-03 17:55

Thanks for your answers Michael & Li, i know i need a CWindowImpl derived class to do the job, but what i mean is, i dont understand the phylosofy (pardon my spelling if wrong, english is not my native language) of the creators of WTL in this issue, because what DDX_CONTROL is supposed to do, its easier done -without- DDX_CONTROL!.
I find it "harder" (more time consuming) to have to write a class(even a small one) for every type of control i want to use, include the proper headers on my dialog class, add the ddx map entry, etc., than just declaring a member variable like CEdit m_MyEdit, or CListViewCtrl m_MyList, etc. and just attaching it via their Attach() method on my dialog´s OnInitDialog(), my point is ¿whats the design concept behind DDX_CONTROL? or in other words, ¿when do you actually use DDX_CONTROL because its easier to do so?