User forums > Using Code::Blocks
Problem with svn 12294
gd_on:
That's what I was afraid of : a full rebuild of svn 12292 has already the problem. I have not seen this before because, generally but not always, I build incrementally successive svn version. So, I suppose that something has changed inside the compiler which impact C::B. But it's now out of my competence, sorry.
Avan:
--- Quote from: MortenMacFly on February 25, 2021, 04:40:13 am ---OK, I wasn't aware that there are still Win7 users around and reverted.
These libs won't work on Win7. On the other hand (sticking with the old ones) the report won't include new APIs, which seems the smaller issue.
For the record: They do work with C::B though. I cannot reproduce the crash reported here. So this might have another reason.
--- End quote ---
I'm on Win7. I'm on 12294. I'm on wx313.
Innitially I had the kernel32 thing too but it went away when I reinstalled my previous wxWidgets folder (dates in that folder back to 27/10/2019 and before).
Setup.h contains:
#define wxUSE_GRAPHICS_DIRECT2D wxUSE_GRAPHICS_CONTEXT
and
static wxFontWeight GetWeightClosestToNumericValue(int numWeight) {
//wxASSERT(numWeight > 0); <--- Disable this line for now
wxASSERT(numWeight <= 1000);
EDIT: I also managed to get it going after copying the missing api dll from C:\Windows\System32\CompatTel to the C::B folder.
Miguel Gimenez:
--- Quote ---I also managed to get it going after copying the missing api dll from C:\Windows\System32\CompatTel to the C::B folder.
--- End quote ---
That dll is there only if you installed the telemetry (read as spying) update, KB2952664. Looks like dbghelp.dll now sends your work to M$.
--- Code: ---static wxFontWeight GetWeightClosestToNumericValue(int numWeight) {
//wxASSERT(numWeight > 0); <--- Disable this line for now
wxASSERT(numWeight <= 1000);
--- End code ---
Why is this needed?
sodev:
Wasn't there a bug in wxWidgets regarding rounding of font sizes resulting in one of such assertions to trigger? His version might be affected by that bug.
Miguel Gimenez:
Thanks, that is it. It was fixed in 19/1/2020, after 3.1.3 release.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version