wxWidgets Discussion Forum

Use wxPixelData to write directly into the bitmap, without the vectors: https://docs.wxwidgets.org/trunk/classwx_pixel_data.html As you're just writing into memory, it's safe from multiple threads. But you must destroy the wxPixelData instance before you use the bitmap for any other operation, like ...

Pass as "style" to the wxWindow ctor. And must not have the "dc.Clear();" in the paint event handler.

mael15 wrote: ↑

Sun Apr 18, 2021 7:57 am

I am wondering why a "simple and clean" EVT_KEY_UP is not triggered while EVT_CHAR is. Any idea?

Not really. Got any sample code i can play around with? I'm lazy on a sunday

Add the wxTRANSPARENT_WINDOW style flag.
Call SetBackgroundStyle(wxBG_STYLE_PAINT); in the ctor, so that its background does not get cleared.

Memory leak: You need to call "delete gc;" at the end of the paint event handler.

int x0=100,y0=100,x1=0,y1=0,x2=0,y2=0,D1=40,D2=60; I suspect these hard-coded coordinates to be responsible. Inside a paint event handler for a specific window, the coordinates are relative to the window position, i.e. they always start at (0,0) in the upper left corner. I guess you're drawing outs...

Is this all about avoiding to delete multiple items because of the key-repeat of the delete key?

Under Windows you can get this information from wxKeyEvent::GetRawKeyFlags(). If bit 30 is set, the event is the result of an auto-repeat.

How exactly did you try to build the samples? They all should build fine from the command line using the provided make files.

If you try to build them in CodeLite, you'll probably have to add the missing libraries to the linker options yourself.

I usually don't work under Linux, but i have a faint memory that window creation under GTK is somehow delayed compared to window creation under Windows. I assume the Layout is calculated before the wxStaticText is aware of its new font size. I thought there was an open ticket about this on http://tr...

The code is a little bit verbose because it comes from wxFormBuilder...

It's horrible indeed. Please remove *all* Fit() and Layout() calls. What happens on the "broken" page when you resize the frame manually?

Off-topic:

i'm still waiting for a reply about the questions i wrote here about the wxStopWatch class members.

I think Vadim gave you a pretty clear answer. And in case you don't know him, he's the main wxWidgets maintainer. His word has weight.

How is that a "small" test case? Small maybe, but not minimal. Is the wxSimpleBook relevant for the problem? Probably not. What about the buttons? I would suspect that a single wxPanel with 3 wxStaticTexts should be sufficient to show the issue.

I don't quite understand the question. Can you show a screenshot?

You can't change the style of the radio buttons. However, they should look exactly like any other native radio button under Windows. If you get an interface that looks like Windows 95, then your executable is missing the manifest file.

I'm not sure it's going to work that way. All the main applications will have their own event loop which will collide with the wxWidgets event loop in your library. Especially in case 2 where the host application does also use wxWidgets. But in that case you could provide a dedicated call in the lib...