wxapp

I'm currently migrating from wxPython 4.0.7 to wxPython 4.1.0. This changes the wx version from 3.0.x to 3.1.x.

Tl;dr: Using a wx.ListCtrl I sometimes get an error when I call event.Skip() inside a wxEVT_SIZE event handler. To Skip() or not to Skip()? (i.e. whats the default event handling for a wxEVT_SIZE and do I need it?)

Long Version:

Using wx.ListCtrl with event.Skip inside the wxEVT_SIZE handler produces an error in some of my forms (so I think there must be more to it). Now, I couldn't strip any of the occurrences down to have a minimal example, since the error kinda disappears randomly when I remove (seemingly) unrelated parts of the code. The error even disappears (sometimes) when I replace a long label with a shorter label. However, changing the Frame or Panel size doesn't change anything.

Here is, what I found out:

• The error is definitely linked to the usage of the wx.ListCtrl class
• The error only occurs, when a function is bound to the wxEVT_COMMAND_LIST_ITEM_ACTIVATED event, though an empty handler (with or without Skip()) is enough to provoke the error.
• The error only occurs when a function is bound to the wxEVT_SIZE event
• The error only occurs when I call event.Skip() in the wxEVT_SIZE handler

It seems like I can simply remove the event.Skip() call inside the wxEVT_SIZE handler and be done, but the relevant C++ Code seems like there is more going on.

Here is the error (note: the error does not crash the wxApp):

I'm using wxPython FlatNotebook widget and have enabled the FNB_X_ON_TAB style. But what bind event triggers on this action (clicking the x in the tab to close it)?

I'm relatively new to both C++ and Wx, so I've been doing a lot of blundering around trying to get this to work over the past few hours, but I seem to have hit a figurative brick wall with this issue.

This code compiles with no errors, but when run, it does nothing. It simply remains running until terminated (e.g. with Ctrl-C), but a window never opens.

Here is the C++ source:

I am making a series of applications on physics simulations and until now I've done some of them using purely the handy SFML library. Now I want to add some GUI elements to them. I am just a little bit familiar with wxWidgets framework and wxFrames but have no idea how wxDc works, which seems to be at the core of SFML-wxWidgets integration. I will list my queries one by one.

1. My shot at the old tutorial provided by SFML dev webpage: The final code, after correcting for the trivial errors looks like this:

I have been trying for a while to get the wxWidgets library working on my Mac, but I have been having tons of issues. I have tried both downloading the source and building it myself and using Homebrew.

I have gotten to the point where I can compile the following:

helloworld.hpp:

I'd like to use wxTimer in my application, but I don't want to use the preprocessor macros to bind the events. Instead I want to use Bind() during the CTOR call to bind the events to my ui elements.
After binding my timer, it doesn't start or it doesn't call the event handler. According to this it ought to work like I want to. I also do not want to use Connect(). Binding a button in the same way works just fine. Here is a minimal example:

minimum example:

I'm new to wxWidgets and I wanted to make a simple GUI application (on ubuntu) for reference.

I created a simple window, added some buttons and in a button event handler I want to update a wxStaticText object's text on screen to indicate which button has been pressed.

However when I call the SetLabel or SetLabelText functions that wxStaticText inherits, then I get a segmentation fault.

Maybe I'm missing something and wxStaticText is just not able to have their label set and I need another control. But I couldn't find anything like that in the class list.

I'm using wxWidgets 3.1.4 from the codelite repositories.

MainFrame.cpp

I have got a class named cApp.

I want to run CheckProcessList() in the background until the program terminates. So i thought, well, lets run it in a detached thread until ~cApp(). I made a bool to break out of the loop in CheckProcessList(). In ~cApp I set the bool true m_bTerminateThread = true to break out and wait for the promise m_barrierFuture->wait() that the thread has ended execution. After breaking out i set the promise barrier.set_value() that the thread is now ending execution. Now ~cApp can finish execution. Or at least that is my understanding of the things i want to achieve and how to do it. Well, can't be right since i get Compiler Errors.

Why did it want to check if the thread finished in the first place? Because the program breaks at runtime when it terminates and the thread is at that moment in GetProcId(). If it is sleeping in the moment of termination the program does not break.

I searched msdn and stackoverflow for answers but i do not get anything out of it that i can understand. I am using VS2019 and C++14. Thank you guys in advance.

cApp.h

I'm trying to create a multithreaded wxWidgets application using the wxThreadHelper mixin. I'm working on Windows, but the whole idea was to be platform independent. I'm basically following the online examples, but there must be something I don't understand, since as soon as I call the Delete() function, the application hangs, waiting forever. The problem is that it appears that the secondary thread hangs also. Do you have any idea on what is it that I'm missing?

This is as minimal as I could get: