I'm noticing a bug where I click on a node sometimes and the cursor
doesn't appear. It's in driver.love, but I can't exclude it might be in
this fork as well. Might as well spread debug prints everywhere I might
catch this.
I'd somehow gotten so used to using the keyboard I forgot I'd supported
the mouse. At least extremely initially.
I think there might still be one bug I haven't been able to reproduce:
sometimes clicking on the nav ends up going to edit.mouse_release with a
nil State. Which means Cursor_node.editor is nil somehow.
Thanks Myte for reporting this bug.
There's one remaining issue: the DOM is changing between mouse press and
mouse release, which is confusing the select handler.
Options:
* some sort of hacky thing to ignore the first mouse release
* put the file picker handlers on mouse release rather than mouse
press
There's some precedent for the latter option even if it might get
confusing in the presence of drag operations. But that seems confusing
either way. Just be consistent.
This will make things more consistent in the long term, but I realize
one major cost: our button abstraction doesn't work well with luaML and
compute_layout. So we need something to replace it.
This required a little more restructuring of Global_state. It's not flat
now, it's hierarchical again, but in a different way.
after commit 3d89b8eb9d:
post
\- reply A
\- reply B
\- reply C
after commit f9f7dab9b7:
post
reply A
reply B
reply C
after this commit:
row
\- col
\- indent 0
\- post
\- col
\- indent 1
\- reply A
\- col
\- indent 2
\- reply B
\- col
\- indent 1
\- reply C
The indents are just invisible rectangles of different widths with 0
height.
One change I had to make was to initialize_editor. Neither luaML and
driver load lines from disk, but that's arguably the common scenario to
support.
Instead of a tree of items, we now have a flat list. Each item knows its
depth. This structure is closer to what luaML's compute_layout needs.
For any future hierarchical functionality, each item still knows its
parent and replies as ids inside the metadata field.
Next step: redo A for this app. compute_layout should stay fairly
timeless across forks of luaML.
Pace layers for apps built on the box model:
A
B
...
F (I think of on.draw as F)
A runs least frequently, F runs on every frame.
In this app, the plan is:
* initialize_thread will load items inside Global_state
* A will convert items into a relatively stable box model of rows,
columns and text editors in Surface, using compute_layout as a
helper.
* B will recompute some aspects of Surface as the viewport moves.
Anything that changes the height of any box needs to rerun A. Anything
that moves the viewport reruns B.