diff options
| author | blasty <blasty@local> | 2026-07-23 23:15:37 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-23 23:15:37 +0200 |
| commit | 279eaeee998fea0b7c8ab2741f6884eb0b80f580 (patch) | |
| tree | 8be195cd41bc7cf750bbce43a3f2a9ca5cf162d0 /tests | |
| parent | fix: refresh-after-edit keeps the edited line on screen (rename now visible) (diff) | |
| download | ida-tui-279eaeee998fea0b7c8ab2741f6884eb0b80f580.tar.gz ida-tui-279eaeee998fea0b7c8ab2741f6884eb0b80f580.tar.xz ida-tui-279eaeee998fea0b7c8ab2741f6884eb0b80f580.zip | |
nav: land the cursor on the ref's column, not column 0
When an xref/follow jump targets a line, the cursor now lands on the COLUMN of
the referenced token (like search does) instead of the start of the line. The
focus_name already threaded into _do_navigate (but unused) is now carried to
_open_at -> _open_entry -> ListingView.load as a one-shot _pending_focus; once
the row is loaded, _on_primed locates the token via _word_occurrences (after the
opcode-column width is finalized) and sets cursor_x, then h-scrolls it into view.
Also pass focus_name from the double-click follow path. When the token isn't on
the destination line (e.g. jumping to a function entry), it's a no-op and the
cursor stays at column 0.
Verified: xref-jump to a 'call sub_2060' site lands cursor_x on 'sub_2060';
follow_xrefs/xref_labels/search/scroll_restore/disasm_nav/mouse/decomp_nav/
listing_view/continuous_view/func_banners/rename/view_toggle 70/0.
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions
