diff options
| author | blasty <blasty@local> | 2026-07-25 20:51:25 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-25 20:51:25 +0200 |
| commit | e7a919f113e7001b83076a1ed7f58bb75caa75a8 (patch) | |
| tree | bcdd3c2ac7b348d0f7b20df3c8bec0e592f34aa5 /server | |
| parent | split: keep _active in step with focus, so Enter follows the pane you're in (diff) | |
| download | ida-tui-e7a919f113e7001b83076a1ed7f58bb75caa75a8.tar.gz ida-tui-e7a919f113e7001b83076a1ed7f58bb75caa75a8.tar.xz ida-tui-e7a919f113e7001b83076a1ed7f58bb75caa75a8.zip | |
split: don't overwrite "decompiling…" with the idle status
Travelling the history stack in split mode showed no feedback at all, so Esc
still read as a no-op whenever the target needed decompiling — the exact thing
cc44f5c was supposed to fix. That commit set the message in action_back, but the
split branch of _show_active ends with _status_for_cur("split"), which
unconditionally wrote the idle status straight over it. The spinner overlay was
already being raised correctly; only the words were lost.
The split branch now keeps the in-flight message while it has just kicked off a
decompile, and on_descendant_focus (added in 190e28b, and firing exactly when
focus lands on the restored pane) no longer restatuses while dec.loading.
Caveat on verification: I could not observe this on targets/echo. Going back
always lands on a function the decompiler has already cached, so the busy branch
completes without a visible frame — sampling the status bar every 60ms across the
whole Esc showed no intermediate state. What's verified here is that the busy
branch sets the message and that nothing downstream clobbers it; the visible
effect needs a target slow enough to decompile, i.e. a real binary.
Suite 192/0.
Diffstat (limited to 'server')
0 files changed, 0 insertions, 0 deletions
