about summary refs log tree commit diff stats
path: root/main.lua
Commit message (Collapse)AuthorAgeFilesLines
* regression: couldn't do many drawing operations because line.y was resetKartik K. Agaram2022-06-041-1/+7
|
* try to maintain a reasonable line widthKartik K. Agaram2022-06-041-15/+15
|
* .Kartik K. Agaram2022-06-041-4/+0
|
* select text with shift + mouseclickKartik K. Agaram2022-06-041-2/+8
| | | | | | | 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.
* bugfix: restore state after C-f (find)Kartik K. Agaram2022-06-031-4/+6
|
* highlight selection while draggingKartik K. Agaram2022-06-031-5/+7
| | | | | | | 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.
* select text using mouse dragKartik K. Agaram2022-06-031-10/+15
| | | | Doesn't yet highlight while dragging.
* renameKartik K. Agaram2022-06-031-2/+2
|
* up arrow to search previousKartik K. Agaram2022-06-031-0/+2
|
* switch copy/paste to ctrl- hotkeysKartik K. Agaram2022-06-021-0/+48
|
* switch undo/redo to ctrl- hotkeysKartik K. Agaram2022-06-021-0/+18
|
* default font size and line-heightKartik K. Agaram2022-06-021-4/+10
|
* extract a new variableKartik K. Agaram2022-06-021-1/+2
|
* crisp font renderingKartik K. Agaram2022-06-021-4/+20
|
* find textKartik K. Agaram2022-06-021-5/+43
|
* .Kartik K. Agaram2022-06-021-1/+1
|
* renameKartik K. Agaram2022-06-021-1/+1
|
* bugfix: undo drawing creationKartik K. Agaram2022-06-021-0/+1
| | | | | Also clean up drawing state to make sure we don't get into hard-to-debug situations.
* after much struggle, a brute-force undoKartik K. Agaram2022-06-021-0/+5
| | | | | | | | | 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.
* .Kartik K. Agaram2022-05-291-6/+0
|
* selecting text and deleting selectionsKartik K. Agaram2022-05-291-0/+11
| | | | | | 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.
* update some documentationKartik K. Agaram2022-05-291-3/+6
|
* move some codeKartik K. Agaram2022-05-281-28/+0
| | | | | I had this idea originally to keep text.lua oblivious to drawings. But that hasn't been true for some time. Losing battle.
* .Kartik K. Agaram2022-05-271-1/+1
|
* assert for a bug I saw a while ago but can no longer reproduceKartik K. Agaram2022-05-251-0/+1
| | | | | I saw screen_top not at start of screen line, but at cursor location in middle of line.
* no, make sure to compute line width after screen dimensionsKartik K. Agaram2022-05-251-4/+4
|
* couple more testsKartik K. Agaram2022-05-251-17/+19
| | | | Along with the App helpers needed for them.
* get rid of debug variablesKartik K. Agaram2022-05-231-9/+4
|
* keep one screen line of overlap on pagedownKartik K. Agaram2022-05-231-1/+1
| | | | | | | | | | | | | | | | | | | | 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-(
* a few tests for pageup, and a bugfixKartik K. Agaram2022-05-231-10/+18
| | | | It wasn't screen-line aware. Now it is.
* disable all debug printsKartik K. Agaram2022-05-231-2/+2
|
* .Kartik K. Agaram2022-05-231-1/+2
|
* couple of tests for cursor downKartik K. Agaram2022-05-231-2/+2
|
* bugfix: don't rely on Screen_bottom1 while scrollingKartik K. Agaram2022-05-231-1/+4
| | | | | Setting up the test just right to test the thing I want to test was a rube goldberg machine of constants.
* first successful pagedown test, first bug found by testKartik K. Agaram2022-05-231-7/+8
| | | | | | | | | | | | | | | | | | | I also really need to rethink how people debug my programs. My approach of inserting and deleting print() takes a lot of commitment. I need my old trace-based whitebox testing idea. However, in my past projects I never did figure out a good framework for tweaking how verbose a trace to emit. Perhaps that's too many knobs. Perhaps we just need a way to run a single test with the most verbose trace possible. Then it's just a matter of having the trace tell a coherent story? But even if the trace stays out of program output in that situation, it's still in the programmer's face in the _code_. Ugh. Current plan: ship program with maximum tests and zero commented-out prints. If you want to debug, insert prints. This is better than previous, text-mode, projects just by virtue of the stdout channel being dedicated to debug stuff.
* fold variables for screen dimensions into the app frameworkKartik K. Agaram2022-05-221-8/+8
|
* basic test-enabled frameworkKartik K. Agaram2022-05-221-26/+25
| | | | | Tests still have a lot of side-effects on the real screen. We'll gradually clean those up.
* renameKartik K. Agaram2022-05-221-1/+3
|
* beginnings of a test harnessKartik K. Agaram2022-05-221-0/+1
| | | | | | | | | | | | | | | | | | | I have no fucking idea what I'm doing. All I know is that there's still too many goddamn bugs[1]. Test motherfucking harness or bust. For starters this is just the default love.run from https://love2d.org/wiki/love.run [1] The following file crashes if you repeatedly press cursor-down: << a b c ```lines ``` x >>
* bugfix: printing the first part of a line at the bottom made it seem ↵Kartik K. Agaram2022-05-211-9/+17
| | | | | | non-wrapping Still lots wrong here.
* I feel confident now that page-down is working.Kartik K. Agaram2022-05-211-2/+3
|
* beginning of a new approach to scroll+wrapKartik K. Agaram2022-05-211-25/+31
| | | | | | | So far I've just changed how existing variables are organized, and put some scaffolding in place for dealing with the new types. Next up: rewriting the code for scrolling to something that feels more obviously correct.
* bugfix: escape key to hide online helpKartik K. Agaram2022-05-211-0/+6
|
* support for naming pointsKartik K. Agaram2022-05-211-0/+27
| | | | There's still an absence of affordance showing when you're in naming mode.
* keep cursor on screen when pressing 'down'Kartik K. Agaram2022-05-201-1/+1
|
* reduce ambitions a bit: page up/down need not start screen from the middle ↵Kartik K. Agaram2022-05-201-13/+14
| | | | | | of a line But we still have work to do for cursor up/down.
* ensure Filename is writable when opened outside a terminalKartik K. Agaram2022-05-201-1/+1
| | | | Thanks Jimmy Miller for reporting this.
* snapshot - no, that's all wrongKartik K. Agaram2022-05-201-9/+11
| | | | | I've been only thinking about up arrow when cursor is at top of screen. Hopefully this is better.
* new globals: draw partial screen line up topKartik K. Agaram2022-05-201-0/+3
| | | | | I'm not setting these yet. Rendering seems to be working after manually setting them.
* start using some globalsKartik K. Agaram2022-05-201-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-05 05:37:13 +0000