gobrad

Thanks Vidar! I investigated the problem a bit further: The most important difference was that my project uses: #define _WIN32_WINNT _WIN32_WINNT_VISTA and OWLNext uses (in wsysinc.h): #define _WIN32_WINNT _WIN32_WINNT_WINXP I am not sure if the logic in wsysinc.h is compatible with the way Windows SDK defines _WIN32_WINNT: If you just install the latest SDK and compile OWLNext and a simple application without setting _WIN32_WINNT explicitly, OWLNExt will default to _WIN32_WINNT_WINXP and the application...

Vidar, thank you for your hints. I've tried adding a destructor in TLvColumn, and it really fixed the problem. So, your assumption was correct. All my builds use static linking, and after checking several time all compiler/linker settings, I could not find any significant differences between my project and the examples. OWLNext libraries are up-to-date, and all projects are using the same libraries in a same way. One more interesting obervation: After turning on aditional compiler/linker checks (SDL...

Hello Ognyan Thank you for looking into this. Since my source code was actually copy/paste from examples, I thought that minimal example would not make much sense. Now I've managed to narrow the problem to this ~~~ { TLvColumn("Column 1", 80); } ~~~ anywhere in my application causes a crash in TLvColumn destructor (presumably) during destruction of the "Buffer" member (std::vector<tchar>). So, even without any dialogs, resources, TListViewCtrl etc. So, I presume that it must be some compiler/linker...

Hello Ognyan Thank you for looking into this. Since my source code was actually copy/paste from examples, I thought that minimal example would not make much sense. Now I've managed to narrow the problem to this ~~~ { TLvColumn("Column 1", 80); } ~~~ anywhere in my application causes a crash in TLvColumn destructor (presumably) during destruction of the "Buffer" member (std::vector<tchar>). So, even without any dialogs, resources, TListViewCtrl etc. So, I presume that it must be some compiler/linker...

Hello Ognyan Thank you for looking into this. Since my source code was actually copy/paste from examples, I thought that minimal example would not make much sense. Now I've managed to narrow the problem to this ~~~ { TLvColumn("Column 1", 80); } ~~~ anywhere in my application causes a crash in TLvColumn destructor (presumably) during destruction of the "Buffer" member (std::vector<tchar>). So, even without any dialogs, resources, TListViewCtrl etc. So, I presume that it must be some compiler/linker...

Hello I am having some problems using TListViewCtrl and I hope that someone can help... My environment: OWLNext 6.44, Visual Studio 2019, 64-bit, fairly mature application using OWLNext for a long time. My problem: I am trying to integrate TListViewCtrl in some of dialogs I am using. To do so, I've took a look at examples (classes\listviewwnd.cpp and some online resources like https://sourceforge.net/p/owlnext/wiki/List%20View%20Control%20tip%20and%20tricks/ ). My implementation looks almost the...

Hi Vidar Thank you for the detailed analysis! It really looks tricky.... would be perfect if each TControl would have a simple SetTooltip(...) method. As for the problem with 24-bit transparent bitmaps.. I've invested some time in it but did not find a solution and finally switched back to 8-bit bitmaps. Best regards Goran

Hi Vidar Thank you, it worked perfectly! Interrestingly, it works only if enabler is in a frame window as in your example. My original enabler was in my TMDIClient window. It received all "normal" enabler calls but not the special ones with TTooltipEnabler. Sorry for the "Anonymous" post, I did not notice that I was not logged in. Best regards Goran