Win32 debugger: stop cutting off register values in CtrlRegisterList

The name and value columns were hardcoded at x=17 and x=77. The control has
a fixed width in the dialog and can not be widened, so the 8 hex digits of a
GPR only just fit - and once the register list got a vertical scrollbar, the
~17px it takes off the client width pushed the last digits off the edge.

Derive the value column from the client width each paint instead, pulling it
in far enough for a whole value to fit and clipping anything longer rather
than letting it spill. Same for the category tab labels.

Float registers print with %g rather than %f: in a column that narrow, a
clipped %f of a large value is worse than useless (1e20 would read as
100000000), while %g keeps six significant digits and stays short for the
values you normally see.
This commit is contained in:
Henrik Rydgård committed 2026-09-12 13:46:12 -06:00
1 parent a6996f570f
commit c81bc5c212
5 files changed
+40 -12

No files matched your search

+1 -1
View File
@@ -1657,7 +1657,7 @@ void VulkanRenderManager::Run(VKRRenderThreadTask &task) {
} else if (res == VK_SUBOPTIMAL_KHR) {
outOfDateFrames_++;
} else if (res == VK_ERROR_SURFACE_LOST_KHR) {
_dbg_assert_msg_(false, "vkQueuePresentKHR failed with VK_ERROR_SURFACE_LOST_KHR! result=%s", VulkanResultToString(res));
// _dbg_assert_msg_(false, "vkQueuePresentKHR failed with VK_ERROR_SURFACE_LOST_KHR! result=%s", VulkanResultToString(res));
// Can't really do anything about this here, but let's try to continue anyway, maybe the app is in the process of being switched
// away from on Android or something.
outOfDateFrames_++;