diff options
| author | blasty <blasty@local> | 2026-07-26 14:36:12 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-26 14:36:12 +0200 |
| commit | c48652464f021f9a86816dd31be6bd6e644a0fd2 (patch) | |
| tree | c478d3c5f1f687e6e319b43bb663018e382a9f3c | |
| parent | app: delete DisasmView, superseded by the unified listing (diff) | |
| download | ida-tui-c48652464f021f9a86816dd31be6bd6e644a0fd2.tar.gz ida-tui-c48652464f021f9a86816dd31be6bd6e644a0fd2.tar.xz ida-tui-c48652464f021f9a86816dd31be6bd6e644a0fd2.zip | |
TODO: DisasmView removed
| -rw-r--r-- | TODO | 11 |
1 files changed, 0 insertions, 11 deletions
@@ -90,14 +90,3 @@ before trusting a failure that appeared without a code change. Coverage for "an edit must not move the view" lives in tests/test_blob_ui.py, which builds its own throwaway binary and can mutate freely. - -## DisasmView looks like dead code - -idatui/app.py defines DisasmView (Line-based, function-scoped) but the app never -instantiates or queries it — the unified ListingView replaced it, and even the -test harness's `Ctx.dis` returns ListingView. DisasmModel is still used, but only -to compute indices in _do_edit_item, never to render. - -Worth confirming and deleting: it's ~180 lines carrying its own rendering, -search and cursor logic that no longer runs, and it misled me into thinking -assembly highlighting needed doing twice. |