What the developer wrote
Authored by Tads
Datum better menu btn offset (#770)
What changed, and why it matters
This commit adjusts the vertical spacing of a menu button in a screen layout. It removes an extra pixel offset so the menu appears in a slightly different position. There is no security relevance visible in the change.
No security action needed. Treat as a normal UI/layout fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch modifies two lines in src/krux/pages/datum_tool.py that compute the Y offset for drawing text and positioning a menu. In both places an extra ‘+1’ or ‘+2’ multiplier/constant is removed, simplifying the layout math. The change is purely cosmetic UI positioning.
Changed components
src/krux/pages/datum_tool.pyInspect captured patch +2 / −2
diff --git a/src/krux/pages/datum_tool.py b/src/krux/pages/datum_tool.py
index 95663db..39c2c96 100644
--- a/src/krux/pages/datum_tool.py
+++ b/src/krux/pages/datum_tool.py
@@ -628,7 +628,7 @@ class DatumTool(Page):
if pages[-1] < endpos < content_len:
pages.append(endpos)
- offset_y = DEFAULT_PADDING + (info_len) * FONT_HEIGHT + 1
+ offset_y = DEFAULT_PADDING + info_len * FONT_HEIGHT + 1
for line in lines:
self.ctx.display.draw_string(offset_x, offset_y, line)
offset_y += FONT_HEIGHT
@@ -822,7 +822,7 @@ class DatumTool(Page):
menu = Menu(
self.ctx,
todo_menu,
- offset=(info_len + 1) * FONT_HEIGHT + DEFAULT_PADDING + 2,
+ offset=info_len * FONT_HEIGHT + DEFAULT_PADDING,
**back_status
)
_, status = menu.run_loop()
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.