 Ryan Fleury
|
4b7e6d7113
|
fixes for variable size rows in new eval visualization structures / integration
|
2024-09-27 10:04:56 -07:00 |
|
|
Ryan Fleury
|
73c37b4d8b
|
correct collection editing/deletion/reordering/etc. with new watch visualization system
|
2024-09-26 16:08:35 -07:00 |
|
|
Ryan Fleury
|
d314a12698
|
eliminate possibility for recursive watch window builds; correctly sort child expansion keys before iteration, if needed, for non-identity-based id schemes (debug info tables, frontend entities, etc.); further fixes & integration
|
2024-09-26 15:26:28 -07:00 |
|
|
Ryan Fleury
|
e705907ec0
|
checkpoint in moving existing watch views to new block-tree visualization structure
|
2024-09-26 08:09:22 -07:00 |
|
|
Ryan Fleury
|
a1ceb5fa3b
|
on second thought... merging both view rule expansion *header* info generation, and windowed range queries into an expanded block, into the same hook, is really limiting & wrong - so split back to two hooks, one stage is just informing the expansion space, the next provides per-row information within an expanded block with range-based queries
|
2024-09-25 15:17:39 -07:00 |
|
|
Ryan Fleury
|
9c3d2cd5ab
|
eval visualization: first pass of new tree-ified block building, which preserves the hierarchy of the eval visualization path, as well as relies on only a single view rule hook; first pass of windowed row list production, given that block tree build; also still just uses the single hook
|
2024-09-25 12:23:50 -07:00 |
|
|
Ryan Fleury
|
c976154284
|
eval: add cache for type data member gathering & member lookup; eval_visualization: sketch out new hook organization which has single hook for both view rule expansion info, + expansion expr production, in a single combined path (the two often require the same information so it is maybe a good idea to combine them - if not, it will be easy to separate into two stages (expand + expr-child production), but basically just trying to get view rules out of 'block production', and more into just providing the information that actually varies per view rule
|
2024-09-25 09:34:23 -07:00 |
|
|
Ryan Fleury
|
fbfaf1c747
|
strip out root buttons idea; fix up pretty member names
|
2024-09-24 11:06:31 -07:00 |
|
|
Ryan Fleury
|
bfe6f655be
|
more work on watch view to replace all old uis
|
2024-09-23 14:26:27 -07:00 |
|
|
Ryan Fleury
|
f728614e0b
|
eliminate watch view fill kind; extend rtti & eval type system with 'external' pointers, for e.g. meta-space vaddr u64s pointing into an address space; begin sketching out paths for mutational rows in watch collections, use to add 'add target' fastpath in targets collection evaluations
|
2024-09-23 10:57:43 -07:00 |
|
|
Ryan Fleury
|
ebaad35813
|
fix filter passthrough & fix double-application of view rules in some cases
|
2024-09-20 17:19:13 -07:00 |
|
|
Ryan Fleury
|
c98db01b63
|
replace watch view fill kind with top-level expression & view rule; collection macro for watches; reintroduce only/omit, with new expr-macro-based eval visualization system; remove root-expression-generation from expansion block generation, since it makes things a bit more complicated
|
2024-09-20 16:15:29 -07:00 |
|
|
Ryan Fleury
|
432e70caf6
|
begin sketching out 'collections', which are the formal mechanism in the eval/eval-viz systems for visualizing synthetic structures/arrays/trees produced by the debugger, rather than ad-hocing / hardwiring the correct ev-block production for each kind of view - the views can still stay, but this is an important feature for other cases
|
2024-09-20 12:04:13 -07:00 |
|
|
Ryan Fleury
|
df4d18aa5c
|
sketch out type-based auto-view-rule in eval visualization system
|
2024-09-19 15:22:47 -07:00 |
|
|
Ryan Fleury
|
bb50e88141
|
eval_visualization layer: builtin view rules, porting of more debug engine code over
|
2024-09-10 16:14:11 -07:00 |
|