wxWidgets Discussion Forum

Problem solved by using good old wxMemoryDC instead of wxGraphicsContext. Thanx for your thoughts, they helped me figuring it out!

I cannot remember needing anti-alias, so I will try drawing without wxGraphicsContext, also try the 2DRenderer you mentioned.
One big difference is using wxPoint in the "normal" drawing and wxPoint2DDouble in the problematic one.

Thank you for your feedback! Apparently you were using the default GDIPlus backend. Try the Direct2D one. Maybe it's faster. -> wxGraphicsRenderer::GetDirect2DRenderer() I could not find this, could you post a link to the documentation please? I actually do not remember why I used a wxGraphicsContex...

i have watched the windows 10 ressource monitor, it seems to freeze when when the amount of "zugesichert" ram exceeds about 60000 kB. does that make sense?!

EDIT: when i wrote this the drawing finished after one minute, so it probably is not a freeze but a very slow drawing.

What's the size of the image and the range of coordinates? image size 724x724, the extreme values of the coodinates are: x: 99,26|477,08 y:-153,42|1310,00 Does it work if you replace DrawLines with StrokeLines? It does not work either. Have you tried reducing the number of points? Yes! It actually ...

Are you saying this code runs in a secondary thread? If yes, try the same code from the main thread. If it works there, you have your answer. If it crashes there too, try decreasing the number of points. Although i couldn't find any documentation that mentions a limit like that in GDI+, i wouldn't ...

I have one of these crashes in a thread with none of the usual debug info. How can I get to the bottom of this? this is the call stack: [Externer Code] > wxmsw31ud_core_vc_x64_custom.dll!GdipDrawLines(Gdiplus::GpGraphics * graphics, Gdiplus::GpPen * pen, const Gdiplus::PointF * points, int count) Ze...

I set a wxCursor using wxSetCursor in an wxEVT_MOTION event. After less than 0.5s the newly set cursor is replaced by the default cursor, so the cursor is flickering when I move the mouse. I see this very clearly when i move the mouse only one pixel. I looked for some other wxSetCursor calls in i.e....

Try wxEVT_TEXT_ENTER instead of wxEVT_COMMAND_ENTER Did not work, seems to be a deeper problem with wxGrid? Like in the other post https://forums.wxwidgets.org/viewtopic.php?f=1&t=45888 where I failed with the tab key? It is a problem to me because I consider it standard behaviour, the user expects...

This has nothing to do with wrapping, but is related to the same example. It try and fail at catching the event of the user pressing enter. Why does this not work?!? #pragma once #include <wx/frame.h> #include <wx/app.h> #include <wx/grid.h> #include "wx/spinctrl.h" class spinNumberEditor : public w...

Devil seems to be in the details with wxGrid. I have a column displaying an angle, so min == 0 and max == 359 and i want the wxGridCellNumberEditorto wrap. So when the wxSpinCtrl shows 0 and the arrow down is pressed, the value should change to 359. I tried these thing unsuccessfully: - Spin()->SetE...

Unfortunately i didn't have enough time tonight to dig deep into it. But i traced through the code and the wxChoice editor definitely gets created and shown, but it closes again very quickly. I think even with CallAfter, the call to EnableCellEditControl() comes too early in this case. The next ste...

Can you strip together a running sample? Yes, at least the tab behaviour can be seen, never mind the not working minus button at the end: #pragma once #include <wx/frame.h> #include <wx/app.h> #include <wx/grid.h> class MyGridCellButtonRenderer : public wxGridCellRenderer { public: MyGridCellButton...

a video would be easies to show this, I try to explain what happens. I have these five columns: string | choice | string | float | custom image a single left click on each shows the editControl just as expected with this code: void onGridLeftClick(wxGridEvent &evt) { CallAfter([this]() { EnableCellE...

doublemax wrote: ↑

Fri May 17, 2019 2:05 pm

Try catching only the wxEVT_GRID_SELECT_CELL event. (Just an idea, untested).

Tried it but it did not work unfortunately.