From a82e311cf19cd5493798b6164e2246f1b78c8bfa Mon Sep 17 00:00:00 2001 From: Rene Gollent Date: Tue, 17 Sep 2013 11:14:38 +0200 Subject: [PATCH] Debugger: Fix calculation in MemoryView. - The offset calculation for mapping the current point wasn't taking into account the number of bytes per hex block, causing it to be proportionally further off if one switched to 16/32/64-bit hex mode. Gets mouse selection working properly in said modes. --- .../debugger/user_interface/gui/inspector_window/MemoryView.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/apps/debugger/user_interface/gui/inspector_window/MemoryView.cpp b/src/apps/debugger/user_interface/gui/inspector_window/MemoryView.cpp index 8b5e782573..7f5111531c 100644 --- a/src/apps/debugger/user_interface/gui/inspector_window/MemoryView.cpp +++ b/src/apps/debugger/user_interface/gui/inspector_window/MemoryView.cpp @@ -677,7 +677,7 @@ MemoryView::_GetOffsetAt(BPoint point) const float blockWidth = (charsPerBlock * 2 + 1) * fCharWidth; int32 containingBlock = int32(floor(point.x / blockWidth)); - return fHexBlocksPerLine * lineNumber + return fHexBlocksPerLine * charsPerBlock * lineNumber + containingBlock * charsPerBlock; }