diff options
| author | blasty <blasty@local> | 2026-07-24 00:05:55 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-24 00:05:55 +0200 |
| commit | 7337bb9e6cbb6ea554e1a155098a19390b9ba45f (patch) | |
| tree | d4a1a3dc0504da0698a0bd17b107f3ca793ac25c /server | |
| parent | ux: label the startup wait as auto-analysis, not "starting a server" (diff) | |
| download | ida-tui-7337bb9e6cbb6ea554e1a155098a19390b9ba45f.tar.gz ida-tui-7337bb9e6cbb6ea554e1a155098a19390b9ba45f.tar.xz ida-tui-7337bb9e6cbb6ea554e1a155098a19390b9ba45f.zip | |
nav: land the decompiler cursor on the function name, not column 0
Jumping to a function in the decompiler (follow/xref into pseudocode) parked the
cursor at column 0 of the prototype line. Now it lands on the function's name in
the prototype instead, mirroring the listing's ref-column behavior.
_do_navigate's prefer_decomp branch: when the target is the function itself
(ea == fn.addr) it uses the prototype line (0) and computes the name's column via
_decomp_col_for; a mid-function target uses the ea-matched line (name column when
present, else 0). The column rides through _open_decomp_entry -> NavEntry
.dec_cursor_x -> _apply_decomp's view.show(cursor_x=...).
Verified: following sub_2060 from pseudocode lands on line 0, cursor_x=28, which
is exactly 'sub_2060' in "unsigned __int64 __fastcall sub_2060(int a1)".
decomp_nav/decomp_follow_self/xref_labels/view_toggle/disasm_nav/search/mouse/
listing_view/continuous_view/func_banners/rename green (follow_xrefs is a
pre-existing ordering flake; passes in isolation).
Diffstat (limited to 'server')
0 files changed, 0 insertions, 0 deletions