diff options
| author | blasty <blasty@local> | 2026-07-24 16:43:36 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-24 16:43:36 +0200 |
| commit | b13b1f181483dfb61d1be1d666f1595b4e7d504f (patch) | |
| tree | a52e87b5e6e7d9e288012d3f5872d98c1c479a9b /server | |
| parent | palette: fix results width (were compounded narrower than the modal) (diff) | |
| download | ida-tui-b13b1f181483dfb61d1be1d666f1595b4e7d504f.tar.gz ida-tui-b13b1f181483dfb61d1be1d666f1595b4e7d504f.tar.xz ida-tui-b13b1f181483dfb61d1be1d666f1595b4e7d504f.zip | |
decomp: restore the 'decompiling…' overlay on F5/Tab from the listing
The F5/Tab-from-listing path decompiled the function inside _decomp_from_listing
(via _decomp_line_for) in a background thread with no overlay, THEN _show_active
re-decompiled it -- but that second call hit the cache and returned instantly, so
dec.loading was set and cleared within a frame and the overlay only flashed. The
long wait (the real decompile) happened with nothing on screen.
Raise the pseudocode pane + loading overlay synchronously in action_toggle_view
before launching the background decompile, so the wait is covered. Non-function
F5 restores the listing via _decomp_from_listing_failed.
Pilot view_toggle now drives the real path (action_toggle_view from the listing)
and asserts the overlay is raised synchronously; F5 paths (decomp_fallback,
continuous_view, region_define) all still pass (20/20 + view_toggle 7/7).
Diffstat (limited to 'server')
0 files changed, 0 insertions, 0 deletions