-
Thanks for your question.
I don't see (yet) why GetApp() causes a problem for your dll. You shouldn't need a dummy CWinApp variable inside your dll.
The dll files are a good place to put resources especially if you're looking to cater for a number of different languages. Win32++ caters for this with the CWinApp::SetResourceHandle function. You would set the resouce handle to the value...
2009-11-25 23:15:36 UTC by david_nash
-
The problem: Win32++ often uses GetApp() to get/set some information. However, when using Win32++ in dialogs which will be built inside a .dll project, there is no need in CWinApp variable because the final dll-file, as a part of another project, just contains some dialog resources and some code, no main window or WindowProc.
So, must I create some dummy CWinApp variable inside a .dll...
2009-11-24 12:39:48 UTC by dv__
-
Welcome back.
I'm looking at dropping the CSplitter class in future releases, as all its features are now catered for by CDocker. If you experience any issues using DirectX inside a Docker's view please get back to me.
Regards,
David.
2009-11-23 23:59:56 UTC by david_nash
-
I had spent lots of time getting to know Win32++ only to realize I wasn't going to be able to use it for the intended purpose. To me it was so obvious that Direct3D must work in every kind of window and not just the main frame. Maybe my frustration came through as impoliteness, I don't know. Anyway I'm happy to hear that Direct3D is now a first class citizen of Win32++ so I'm going to try it...
2009-11-23 14:00:23 UTC by ulfjo721
-
Well, you are absolutely right. Windows programming GDI resource leaks are every bit as serious than memory leaks. This problem happened to me yesterday and I have spent the whole day to solve this problem.
Thank you very much. Thank you for win32++.
Hopely to see more exciting features in the next version.
Best wishes.
2009-11-20 01:14:22 UTC by cnhnyu
-
Thanks for your question (although it belongs in a new thread in my opinion).
Yes memory leaks is a very important issue for any C++ program, not just Win32++. Memory leaks are just one of a set of memory releated bugs that can affect C++ programs (others include dangling pointers and buffer overruns).
Memory leaks are invariably associated with memory allocated off the heap. Thats to say...
2009-11-19 04:48:09 UTC by david_nash
-
Well, I found a very important question when I am using this framework. I don't know how to detect memory leaks. I know it does exist, but I've got not idea to find it out. Can you give me a piece of advice on this problem ? Thank you.
2009-11-19 02:44:58 UTC by cnhnyu
-
David, thank you very much for your reply! It saved a lot of my time. Finally I've decided to create the toolbar using CreateEx:
OnInitDialog()
{
m\_toolbar.CreateEx(0, TOOLBARCLASSNAME, \_T(""),
WS\_TABSTOP | WS\_VISIBLE | WS\_CHILD | TBSTYLE\_FLAT, 1, 1, 0, 0, m_hWnd, NULL);
...
}.
2009-11-18 17:38:29 UTC by dv__
-
I've posted an update (available via SVN) which moves the files for the static library to a "StaticLibrary" folder. The relevent header files are located within the "src" sub directory of this folder. This should eliminate any confusion between the static version and the normal inline version of the Win32++ library.
Regards,
David.
2009-11-18 12:44:17 UTC by david_nash
-
david_nash committed revision 1011 to the Win32++ SVN repository, changing 1 files.
2009-11-18 04:00:26 UTC by david_nash
