wxWidgets Discussion Forum

FWIW: If you use VS anyway, i recommend crashrpt, much more powerful: http://crashrpt.sourceforge.net/ Finally got crashrpt installed, compiled and linked into one of my smallish test programs. It seems that the project is now abandon-ware and since my work with this code thus far has raised a numb...

same issue with MSVC 2015 & 2017
Will look into crashrpt - had downloaded it some time ago, but never spent the time to test it and replace my existing code. Looks like now is the time to do so
Thank you all

3.1.3 (32-bit) debug version shows the same problem, I'm afraid

All libraries are built by myself, using the same IDE as for the samples All testing dome under the up-to-date Win 10 OS with an up-to-date MSVC community edition IDE the full stack trace at the time of the crash below - with the Exception message: Exception thrown at 0x76F341CA (kernel32.dll) in de...

After trying to use debug reporting & having issues with my own code - which follows the example in samples, I tried the sample project, but it will not run at all under MSVC 2019 IDE. Using any of the report options, it crashes with Exception thrown at 0x76F341CA (kernel32.dll) in debugrpt.exe: 0xC...

@DM & PB
Thank you both for the clarifications

so the queue is really used mainly for feedback to the secondary thread and one still would need to use an event to initiate any action in the main thread, with possibly extra information via the queue?

I know this is an old thread, but rather than start over I would like to ask where in the main app one would wait for feedback from the secondary thread via the message queue?
Via events or in OnIdle, OnUiUpdate?
TIA

That may well be the best option
For my current apps, I am really only interested in getting a thumbnail and checking for minimal compliance with the TIFF standards,
Will have to see if libtiff will give me that much. Though it would be preferable not to have to treat TIFFs as a special case.

After implementing the sub-classed log code, I can intercept the error messages produced by calls to wxLogError & wxLogWarning by code deep inside wxImage:: LoadFile() but the calls to the intercept logic are delayed by way too much time to be usable in the code after the call to LoadFile() returns....

Initially, I had used wxLogNull, but I ended up with some very puzzling situations because of errors from deep within the wxWidgets code (failure to allocate enough memory) and that is what got me to this point. I do want/need to intercept these errors and display them to the user with more details ...

Thank you. I'll have to wrap my head around all of this; fortunately it triggered some memories of another wxLog related issue - years ago - where I needed to filter out only certain messages; see the earlier discussion: https://forums.wxwidgets.org/viewtopic.php?t=44070 As time permits, I will try ...

In my current app I need to analyze images of various formats and sizes. All regular app error messages are redirected to a log window -> wxTextCtrl. The problem I am running into for some large image files, mainly 50 - 100 MB TIF files, is, that the image handler code does not succeed in allocating...

Thank you both,
Fortunately, it is only Windows I am concerned about, it is a purely 'local' utility.
As for the 'gotcha', I'll have to consider if it is important enough and then which way to go.
Then again, it might be 'educational' to try it.

Is there any way I can force the zebra striping or do I need to manage it myself when the list is redrawn? or using UpdateUI? EraseBackground?
It all works OK, if I disable the assert line, but, of course, no striping