wxWidgets Discussion Forum

My latest tests using the latest code for wxWidgets from Github show no problems with hanging at all. The 32-bit debug version compiled & ran to completion without a hitch. It still shows piles of memory leak though. As well, a very cursory check shows that a lot more of the test have been ported to...

Eventually I will get there and report back.
But right now, getting things at least sort-of-working will take precedence

What I have done: Download the wxWidgets 3.1.2 package for Windows Install it all and build my libraries - mainly for statically linked 32-bit apps. Root for the wxWidgets 3.1.2 tree: D:\MSVC2019\wxWidgets-3.1.2\ Cd to the directory D:\MSVC2019\wxWidgets-3.1.2\tests Open the .sln file test_gui_vc15....

The best way to start something with wxWidgets is to copy the appropriate sample folder, strip it and then add your own code. I would guess that it is the same in your case. Well, the 'test' tree is quite large, but if that is the only way ..... Well, does it finish without any assertions or crash?...

Although I have used some unit tests with cppUnit before, I just came across Catch2 and the test samples in the wxWidgets source tree. After reading the recommended how-to-write-unit-tests.md, and compiling and running the GUI test sample, I still have some very basic questions about how I would go ...

Hi, First of all you don't need to use anything to build the samples. Every sample directory contains the project file which you can open and build from. They are located inside wxWidgets\samples\{minimal} as minimal.vc{X}. Second - you didn't clone the sources correctly. You should be using: git c...

I've run into the same issue as the OP Using the provided sln file for 3.1.2, I have been able to build the libraries I want, but I also wanted to compile all of the samples. These are not part of the 3.1.2 sln. Rather than trying to build a new project for all of the samples within the given sln fi...

What is the result of doing, in a terminal: wx-config --cxxflags --libs ....@Xeon-Mint-19:~$ wx-config --cxxflags --libs -I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread -L/usr/lib/x86_64-linux-gnu -pthread -lwx_g...

3.1.3 might be possible, but more work.
Was there a major change in platform.h?? surely others must have used CMake before this?

IIRC, the options were ../configure --with-gtk --disable-shared --with-zlib=$HOME/wxWidgets-3.1.2/zlib

I am trying to compile a project (wxWidgets 3.1.2) using Cmake under Mint 19.2 and I keep getting a number of error "#if with no expression" for the line #if wxUSE_UNICODE in platform.h and that is a show stopper Cmake's 'Configure' & 'Generate' seem happy enough, aside from a comment about a policy...

ONEEYEMAN wrote: ↑

Wed Oct 23, 2019 9:01 pm

Hi,
Is there something in the BIOS which will configure which monitor will be primary?

Thank you.

No, nothing; it is a Windows construct/concept.
There seems to be some sort of ordering, but I don't know if it is the BIOS or some lower level of Windows.

I have tried tracing into the code but cannot see where or why I do not get the answers I expected, nor can I resolve in my own mind, why what I do get is, in fact, correct. There seem to be other weird (read: unexpected) things happening with my screens/monitors. My graphics outputs are from 2 on-b...

Hi, wxWidgets provides the "persistence framework". Maybe this will work better for you? Check this for reference. Thank you. This is an interesting part of wxWidgets, but won't help me here because 1)the problem is not in 'remembering' coordinates, but in understanding the Win way of doing things ...

Did you check that wxDisplay actually returns the correct rect for each display? int n = wxDisplay::GetCount(); for(int i=0; i<n; i++) { wxDisplay display(i); wxRect r = display.GetGeometry(); wxLogMessage("screen %d: %d,%d %d,%d", i, r.x, r.y, r.width,r.height ); } After modifying the code to send...

As this problem starts out from a wxWidgets project, I am posting the question here, though I perhaps should ask on a Windows forum? Running the most recent update of Win 10 64-bit 3 monitors with 1920x1080 resolution, same size, but different manufacturers. MSVC 2017 Community edition, WxWidgets 3....