Activity for gobrad
-
gobrad posted a comment on discussion Open Discussion
Thank you Vidar, I've missed that feature request. It describes my problem very well. I will try to find some time to tackle the toolbar problem in the next months. Before I implement the solution recommended from Luigi, I will investigate some more generic solutions first. If I come up with a solution which can be integrated in OWLNext, I will let you know. Best regards Goran
-
Dear Luigi Thank you for a fast response! Yes, I was afraid that it is the only option. I have >100 24x24px bitmaps in the software, and have to find a way to resize them in acceptable quality first. The idea with the offset between bitmaps and your GetDPI functions are very helpfull! Best regards Goran
-
Hi I am trying to adapt my OWLNext (6.44) application better to High DPI displays. Automatic Windows scaling ("scaling performed by system") results in a blurry UI, and without it, my UI elements are sometimes too small. Are there any experiences or best practices about handling High-DPI subject with OWLNext? I've already added various functions enabling user to adjust the size of the graphical output of the application, but still have the problem that toolbar and its buttons are sometimes too small....
-
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
-
Hello I would like to create 24 or 32-bit bitmaps and use them in a toolbar with TButtonGadget and TControlBar. How can I set transparent color for such bitmaps? If I try creating 32-bit RGBA bitmaps with proper transparent color, the transparency is ignored and black background is shown in a toolbar. If I use PNGs with transparent color set, I get an exception inside TButtonGadget during creation. It seems that PNgs are not supported as a bitmap resource? Can someone describe a process/toolchain...
1