wxWidgets Discussion Forum

The list stores pointers any you're passing the same pointer (&i) for every element.

Use STL containers or the wx wrappers: https://docs.wxwidgets.org/trunk/group_ ... iners.html

You can't get a filedescriptor from a wxMemoryInputStream, but since libvlc 3.0.0 there is another way:
https://www.videolan.org/developers/vlc ... 2b9b75d8e2

I didn't check the whole code myself, but what you're saying sounds plausible.

Please open a ticket at http://trac.wxwidgets.org

g_my_windows_message = RegisterWindowMessage(TEXT("SomeMessage")); /// WXLRESULT MyFrame::MSWWindowProc(WXUINT nMsg, WXWPARAM wParam, WXLPARAM lParam) { if ( nMsg == g_my_windows_message ) { // do your stuff here return TRUE; } return wxFrame::MSWWindowProc(nMsg, wParam, lParam); }

You can't use "normal" wxEvents to communicate between applications. For communication between two wxWidgets apps check this: https://docs.wxwidgets.org/trunk/overview_ipc.html Under Windows there is a simple way by using "RegisterWindowMessage". https://docs.microsoft.com/en-us/...

I have no idea who's responsible for the Wiki page, try asking on the wx-users group / mailing list.
https://groups.google.com/forum/#!forum/wx-users

The VS project files for all samples use relative paths for include, library and resource directories. If you move them, you need to adjust these under:
C/C++ -> General
Linker -> General
Resources -> General

At the very least you should have seen fewer errors. Did you or did you get the same ones as before?

copying these files to wxWidgets lib/gcc_lib folder.

That should not be necessary and usually does more harm than good. Reverse it.

I can't give you a "oh, yeah, that was fixed in...", but based on the screenshot, it could be a High-DPI problem. Is your program marked as "DPI aware"? If yes, try setting the font-scaling on your system to 150 or even 200% and check if you then see the issue.

I'm no Linux expert, but to me it sounds like you're running out of memory. How much RAM does the PC have?

Try "make -j2" to use only 2 cores.

It is legal to have multiple event handlers for the same event for the same wxEvtHandler object, yes?

Probably yes. (not 100% sure though). But only the the first one will get executed unless it calls "wxEvent::Skip()".

I'm doing the Bind() inside Create(), near the end.

Yes, but do you call Create() for the base class or create it in any other way?

For instance, if I change the superclass (for the class in question) to a class that has a wxEraseEvent handler Bind()'d, the superclass's handler gets called, but not the subclass's. That's interesting. Is the base class already fully created when you make the Bind call? For a test, can you try us...

Puh! (...once again). Some days ago, i had a problem with my compiler-settings. It took me more then one day to get it to work again. Concerning this, i'm quiet stupid. I would like to learn more about this (i also still use the even more ancient devC-IDE, because until now i was not able to compil...

I can also put a breakpoint in wxWindowMSW::MSWHandleMessage() [src/msw/window.cpp] and see that the windows message is coming in for my object. In that case, why didn't you step a little further into the code and see where it takes you? In the whole path there few conditions that could prevent the...