1
Help / Re: Debug Report popup message then crash
« Last post by Miguel Gimenez on Today at 12:11:43 pm »Future spam added to radar...
News:
When registered with our forums, feel free to send a "here I am" post here to differ human beings from SPAM bots.
Recent Posts
2
Nightly builds / Re: The 22 July 2023 build (13319) is out.
« Last post by Miguel Gimenez on Today at 12:10:17 pm »Future spam added to radar...
3
Help / Re: Debug Report popup message then crash
« Last post by HiramWindler on Today at 12:09:17 pm »It seems that the current version does not have the feature to store information after reopening the file. Please wait for the new update. 
4
Plugins development / Re: FromDIP need in the wxSmith generated code?
« Last post by ollydbg on Today at 11:38:55 am »OK, I think we can wait until wxSmith drops the wx 3.0 support. 
5
Nightly builds / Re: The 22 July 2023 build (13319) is out.
« Last post by RonaldGilmore on Today at 10:44:03 am »It appears you've provided information about a nightly build and updates for Code::Blocks using GCC 13.1.0. Users can download the new wx/mingw dll's and access relevant links. Ensure to check the RSS feed for quick announcements. Be aware of how nightly builds work before use.
6
Plugins development / Re: FromDIP need in the wxSmith generated code?
« Last post by Miguel Gimenez on Today at 09:44:57 am »A search for FromDIP() in wxSmith returned nothing.
Fortunately, code generation for wxSize and wxPoint is centralized in wxspositionsizeproperty.cpp and wxsdimensionproperty.cpp. On the other side, wxSmith does not use FromDIP() itself, so it must be heavily edited.
Adding the FromDIP() may break existing wxSmith dialogs, but HiDPI in wxwidgets is so new that IMHO they will not be a lot.
EDIT: FromDIP() was added in wx3.1.0, but we still support wx3.0.x for C::B itself and code generated by wxSmith.
Fortunately, code generation for wxSize and wxPoint is centralized in wxspositionsizeproperty.cpp and wxsdimensionproperty.cpp. On the other side, wxSmith does not use FromDIP() itself, so it must be heavily edited.
Adding the FromDIP() may break existing wxSmith dialogs, but HiDPI in wxwidgets is so new that IMHO they will not be a lot.
EDIT: FromDIP() was added in wx3.1.0, but we still support wx3.0.x for C::B itself and code generated by wxSmith.
7
Plugins development / FromDIP need in the wxSmith generated code?
« Last post by ollydbg on Today at 09:09:13 am »Hi, it looks like there are so many monitors which has DPI scaling such as 150% or 200%.
I found that some wxSmith generated GUI works OK in one PC, but works badly on another PC. My guess is that the code generated by wxSmith is not using the FromDIP function call, so it can't handle the DPI issue.
Any ideas?
I found that some wxSmith generated GUI works OK in one PC, but works badly on another PC. My guess is that the code generated by wxSmith is not using the FromDIP function call, so it can't handle the DPI issue.
Any ideas?
8
Using Code::Blocks / Re: How to view YMM and ZMM registers in watches window?
« Last post by VbCl8ye2vyFPaP0M on Yesterday at 06:33:33 pm »Sorry about that, it seems to be a problem with GDB rather than Code::Blocks.
I'm using "GNU gdb (GDB) 13.2". It disassembles the code correctly with AVX2 instructions and ymm registers, but no amount of googling and trying commands in the console will make it print the value of YMM registers :-(
I'm using "GNU gdb (GDB) 13.2". It disassembles the code correctly with AVX2 instructions and ymm registers, but no amount of googling and trying commands in the console will make it print the value of YMM registers :-(
9
Using Code::Blocks / Re: How to view YMM and ZMM registers in watches window?
« Last post by Miguel Gimenez on Yesterday at 12:34:22 pm »Probably they have no associated types (256 and 512 bits are too big).
10
Using Code::Blocks / How to view YMM and ZMM registers in watches window?
« Last post by VbCl8ye2vyFPaP0M on Yesterday at 01:26:44 am »Is there a way to view the YMM and ZMM registers in the watches window? Viewing $xmm0 shows the contents of XMM0 as expected, but $ymm0 and $zmm0 just shows the the text "void" and the type void.
Using
Version : 20.03-r11983 (on Windows 7 x64)
P.S.: $rflags or $flags also show 2 x void, but $eflags does work.
Using
Version : 20.03-r11983 (on Windows 7 x64)
P.S.: $rflags or $flags also show 2 x void, but $eflags does work.