• Advertisement

Archived

This topic is now archived and is closed to further replies.

WTL pains

This topic is 5188 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Advertisement
First off, I''ve only been messing with the WTL for a couple days now so I may not have the best info for you.

If I understand you question correctly, then all you need to do is have your child frame''s view object inherit from CDialogImpl. This is how the WTL wizard sets things up and so far it seems to work fine for me.

Share this post


Link to post
Share on other sites
Well, I took your advice and installed the AppWizard; I successfully hacked the code to do what I wanted. What I don''t quite understand is why this worked, when I was doing the same thing in my own code; yet it failed to work?

Anyway, it''s all done now. The next question will be coming when I find teething troubles using WTL windows from a DLL. I hope that THAT''S not going to be an issue.

From what seems to be a useful template package, it''s a total pain in the ass to get working properly

Share this post


Link to post
Share on other sites
There''s nothing different about using WTL in a DLL as compared to using it in an EXE. You simply call _Module.Init(instance, 0); on DLL_PROCESS_ATTACH and _Module.Term(); on DLL_PROCESS_DETACH.

Share this post


Link to post
Share on other sites

  • Advertisement