sokoban.love/0004-on.update

on.update = function(dt)
	refresh_debug_animations()
	if Active_button and Active_button.expire <= Current_time then
		Active_button = nil
	end
	if Selected_slider then
		update_any_sliders(App.mouse_x(), App.mouse_y())
	end
	if Current_pane.editor_state.scrollbar_drag then
		adjust_scrollbar(Current_pane.editor_state, App.mouse_y())
	elseif Current_pane.output_editor_state.scrollbar_drag then
		adjust_scrollbar(Current_pane.output_editor_state, App.mouse_y())
	end
	if car.update then call_protected(car.update, dt) end
end
support event handlers I've agonized over conflicts between editor and script handlers for a while, but finally the solution occurred to me: to use the script's handlers, hide the editor. To use the editor's handlers, show the editor. The menu and settings are always active. This seems nice and consistent, easy to explain. Mike Stein would prefer we just supported love.* handlers in scripts to minimize special cases and cognitive load for people. But I'd rather err on the side of being transparent about what's going on inside. As a compromise I'm supporting love.* names at least in addition to my rephrasings (which came about mostly because love.keychordpressed is just too much of a mouthful) 2023-11-22 03:17:49 +00:00			`on.update = function(dt)`
debug animations https://merveilles.town/@akkartik/111333888472146119 2023-11-11 18:00:54 +00:00			`refresh_debug_animations()`
activate buttons for some time The active state has 2 uses: * It gives some visual feedback that a button has been pressed. Otherwise, tapping a button gave no feedback that the tap had occurred. Particularly on a phone screen where fat-fingering is easier, hitting the 'save' button in particular gave no hint that the file had actually been saved. Which causes some anxiety. * It suppresses all mouse taps during the activation time. For example, this helps keep tapping say an overflow button from selecting text in the editor. 2023-12-02 04:07:20 +00:00			`if Active_button and Active_button.expire <= Current_time then`
			`Active_button = nil`
			`end`
check slider state more precisely 2023-12-02 04:53:08 +00:00			`if Selected_slider then`
sliders for font size and color settings 2023-11-21 10:19:56 +00:00			`update_any_sliders(App.mouse_x(), App.mouse_y())`
			`end`
aggregate global state inside a 'pane' object We're soon going to start juggling multiple of these. 2023-11-19 21:15:06 +00:00			`if Current_pane.editor_state.scrollbar_drag then`
			`adjust_scrollbar(Current_pane.editor_state, App.mouse_y())`
			`elseif Current_pane.output_editor_state.scrollbar_drag then`
			`adjust_scrollbar(Current_pane.output_editor_state, App.mouse_y())`
mouse events for scrollbar You can either drag the scrollbar or click anywhere in the scrollbar area. It has this weird funkiness that the scrollbar shrinks as you get near the bottom. But it feels.. weirdly satisfying? 2023-11-18 13:26:28 +00:00			`end`
send errors from event handlers to output editor 2023-11-22 05:10:38 +00:00			`if car.update then call_protected(car.update, dt) end`
activate buttons for some time The active state has 2 uses: * It gives some visual feedback that a button has been pressed. Otherwise, tapping a button gave no feedback that the tap had occurred. Particularly on a phone screen where fat-fingering is easier, hitting the 'save' button in particular gave no hint that the file had actually been saved. Which causes some anxiety. * It suppresses all mouse taps during the activation time. For example, this helps keep tapping say an overflow button from selecting text in the editor. 2023-12-02 04:07:20 +00:00			`end`