| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
The hard part here is keeping click-drag selection working (without
pressing and holding shift).
|
| | |
|
| |
|
|
|
|
|
|
|
| |
I've tried to keep the time period of the blinking similar to my
terminal.
Honestly I'm no longer sure if any of my experiments are showing a
statistically significant result. Let's see how it feels over a period
of time.
|
| |
|
|
| |
This seems to speed up copy! What does it slow down?
|
| |
|
|
| |
Thanks John Blommers for the report!
|
| |
|
|
| |
Hopefully there won't be too many others.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This still isn't ideal. On my Linux laptop for some reason the window
receives a signal to maximize itself soon after (but sometime after) the
program starts.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
I'm being unprincipled at the moment between pos and x,y coordinates.
Whatever is more convenient. Perhaps a cleaner approach will come to me
over time.
|
| | |
|
| |
|
|
|
| |
Why are we not modifying Screen_top1.pos in these places? Because we
don't really need to modify Screen_top1 at all.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
It's still a bit simple-minded. Most software will keep the first bound
fixed and move the second. Lines currently has the bounds in a queue of
sorts. But I have a test to indicate the behavior that is definitely
desired. We'll see if we need it to get more complex.
|
| | |
|
| |
|
|
|
|
|
| |
Mouse stuff is pretty strenuous. For the first time I have to be careful
not to recompute too often. And I ran into a race condition for the
first time where resetting line.y within App.draw meant mouse clicks
were extremely unlikely to see line.y set.
|
| |
|
|
| |
Doesn't yet highlight while dragging.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Also clean up drawing state to make sure we don't get into hard-to-debug
situations.
|
| |
|
|
|
|
|
|
|
| |
Incredibly inefficient, but I don't yet know how to efficiently encode
undo mutations that can span multiple lines.
There seems to be one bug related to creating new drawings; they're not
spawning events and undoing past drawing creation has some weird
artifacts. Redo seems to consistently work, though.
|
| | |
|
| |
|
|
|
|
| |
I've written a few tests for delete_selection, but the way different
operations initialize the selection seems fairly standard and not worth
testing so far.
|
| | |
|
| |
|
|
|
| |
I had this idea originally to keep text.lua oblivious to drawings.
But that hasn't been true for some time. Losing battle.
|
| | |
|
| |
|
|
|
| |
I saw screen_top not at start of screen line, but at cursor location in
middle of line.
|
| | |
|
| |
|
|
| |
Along with the App helpers needed for them.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm now extracting the concern of computing
line.screen_line_starting_pos out of Text.draw. Earlier
I had to make sure I ran through the whole line to compute
screen_line_starting_pos, but that had the side-effect of updating
Screen_bottom1.pos as well with lines that had never been rendered.
In this process I hit my first bug due to an accidental global. It
doesn't show up in the patch because I accidentally deleted a local
declaration. (I thought I didn't need screen_line_starting_pos anymore,
deleted everywhere, then brought it back everywhere from the bottom of
the function up, but forgot to put back the very first occurrence.)
The amount of yoyoing this caused between App.draw and Text.draw, I very
much have spaghetti on my hands.
Accidental globals are _terrible_ in a program with tests. Cross test
contamination X-(
|
| |
|
|
| |
It wasn't screen-line aware. Now it is.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Setting up the test just right to test the thing I want to test was a
rube goldberg machine of constants.
|