a bug I've never run into
[?]
Jul 13, 2022, 3:38 PM
WLWNS6FBT6D3HKOFWDPBKLK7KS73LJJLWLHNWX3YJ723OHJBZGDQCDependencies
- [2]
BXJMGTV2hoist couple of variables out - [3]
RT6EV6OPdelegate update events to drawings - [4]
DRFE3B3Zmouse buttons are integers, not strings - [5]
2L5MEZV3experiment: new edit namespace - [6]
PTDO2SOTadd state arg to schedule_save - [7]
JFFUF5ALoverride mouse state lookups in tests - [8]
QCPXQ2E3add state arg to a few functions - [9]
LF7BWEG4group all editor globals - [10]
7SFHSB47rename - [11]
EHSUSZMKmore idiomatic variable names - [12]
PJEQCTBLadd state arg to Drawing.update - [13]
LNUHQOGHstart passing in Editor_state explicitly - [*]
K2X6G75Zstart writing some tests for drawings - [*]
T7SJSJIHtest: undo naming a point - [*]
BLWAYPKVextract a module
Change contents
- replacement in edit.lua at line 355
Text.redraw_all(State) -- if we're scrolling, reclaim all fragments to avoid memory leaks-- invalidate various cached bits of linesState.lines.current_drawing = nil-- if we're scrolling, reclaim all fragments to avoid memory leaksText.redraw_all(State) - replacement in edit.lua at line 370
Text.redraw_all(State) -- if we're scrolling, reclaim all fragments to avoid memory leaks-- invalidate various cached bits of linesState.lines.current_drawing = nil-- if we're scrolling, reclaim all fragments to avoid memory leaksText.redraw_all(State) - edit in drawing_tests.lua at line 646
--? print('a', Editor_state.lines.current_drawing) - edit in drawing_tests.lua at line 654
--? print('b', Editor_state.lines.current_drawing) - edit in drawing.lua at line 244
if drawing.y == nil thenreturn -- first draw?end