diff options
| author | blasty <blasty@local> | 2026-07-23 22:36:12 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-23 22:36:12 +0200 |
| commit | c24afb90c575bd2950a5fbfbc4b86c6253db2566 (patch) | |
| tree | 037292fc745544abbbbfeca2c75e7b4ba6f8ed6b /server | |
| parent | listing: on-screen jumps just move the cursor, don't re-scroll (diff) | |
| download | ida-tui-c24afb90c575bd2950a5fbfbc4b86c6253db2566.tar.gz ida-tui-c24afb90c575bd2950a5fbfbc4b86c6253db2566.tar.xz ida-tui-c24afb90c575bd2950a5fbfbc4b86c6253db2566.zip | |
nav: jumping from the decompiler stays in the decompiler
Following a reference or picking an xref target from the pseudocode dropped you
back into the linear listing. Now such jumps stay in the decompiler when the
target is a decompilable function, landing on the pseudocode line that matches
the target address; non-decompilable targets still fall back to the listing.
* NavEntry gains a `view` field ("listing"/"decomp"); _open_entry restores an
entry in whichever view it was seen in (so back/forward also keep pseudocode).
* _do_navigate/_goto_ea take prefer_decomp; when set and the target function
decompiles, _open_decomp_entry opens it in the decompiler as a real nav-history
push (snapshotting the source pseudocode position so 'back' returns to it).
* _follow_decomp and _on_xref_chosen pass prefer_decomp when the source view is
the decompiler.
Verified: follow a ref from decomp -> lands in the target's pseudocode; 'back'
returns to the source pseudocode; listing follow still lands in the listing.
decomp_nav/decomp_follow_self/follow_xrefs/xref_labels/view_toggle/disasm_nav/
search/mouse/listing_view/func_banners/continuous_view 62/0.
Diffstat (limited to 'server')
0 files changed, 0 insertions, 0 deletions