template-carousel-mobile/0014-on.text_input

on.text_input = function(t)
	if Show_code then
		if Show_file_dialog then
			text_input_on_file_dialog(t)
		elseif Current_pane.editor_state.cursor_x then
			edit.text_input(Current_pane.editor_state, t)
		end
	else
		if car.text_input then
			call_protected(car.text_input, t)
		end
		if car.textinput then
			call_protected(car.textinput, t)
		end
	end
end
new fork: carousel shell 2023-11-15 14:06:56 +00:00			`on.text_input = function(t)`
switch all handlers to run either the app or editor 2024-01-01 00:21:21 +00:00			`if Show_code then`
			`if Show_file_dialog then`
			`text_input_on_file_dialog(t)`
			`elseif Current_pane.editor_state.cursor_x then`
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			`edit.text_input(Current_pane.editor_state, t)`
			`end`
			`else`
send errors from event handlers to output editor 2023-11-22 05:10:38 +00:00			`if car.text_input then`
			`call_protected(car.text_input, t)`
			`end`
			`if car.textinput then`
			`call_protected(car.textinput, t)`
			`end`
get rid of an assertion It's easy for cursor to go off viewport, and that seems fine. Just don't let a cursor off screen receive keys. 2023-11-20 18:26:14 +00:00			`end`
new fork: carousel shell 2023-11-15 14:06:56 +00:00			`end`