mirrors/foot
1
0
Fork 0
mirror of https://codeberg.org/dnkl/foot.git synced 2026-02-11 04:27:49 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
foot/grid.h

33 lines
1.1 KiB
C
Raw Normal View History

wip: vt parsing: break out grid operating functions
2019-06-17 19:33:10 +02:00
#pragma once
#include "terminal.h"
scroll-region: don't clear damage queue when changing scroll region Vim, for example, changes the scroll region every time you scroll a single line. Thus, resetting the damage queue is slow. This reworks the damage handling of scroll updates: * Split damage queue into two: one for scroll operations and one for update/erase operations. * Don't separate update/erase operations inside/outside the scroll region * Store the current scroll region in the scroll damage operation. This allows us to stack multiple scroll operations with different scroll regions. * When updating update/erase operations after a scroll operation, split the update/erase operations if necessary (the current scroll operation may have a scroll region different from before, thus forcing us to split existing update/erase operations. * The renderer no longer erases after a scroll. The scroll operation also adds an erase operation. This also means that erase operation are subject to adjustments by later scroll operations.
2019-06-25 20:11:08 +02:00
void grid_damage_all(struct grid *grid);
Use a 'damage' list to communicate what needs to be updated Instead of having each cell in the grid track it's own dirtiness, grid operations now append "damage" to a list. This list is consumed every time we render the grid. This allows us to special case some operations, like erase (and in the future, scroll).
2019-06-19 14:17:43 +02:00
void grid_damage_update(struct grid *grid, int start, int length);
void grid_damage_erase(struct grid *grid, int start, int length);
grid: implement DAMAGE_SCROLL
2019-06-21 14:29:15 +02:00
void grid_damage_scroll(
scroll-region: don't clear damage queue when changing scroll region Vim, for example, changes the scroll region every time you scroll a single line. Thus, resetting the damage queue is slow. This reworks the damage handling of scroll updates: * Split damage queue into two: one for scroll operations and one for update/erase operations. * Don't separate update/erase operations inside/outside the scroll region * Store the current scroll region in the scroll damage operation. This allows us to stack multiple scroll operations with different scroll regions. * When updating update/erase operations after a scroll operation, split the update/erase operations if necessary (the current scroll operation may have a scroll region different from before, thus forcing us to split existing update/erase operations. * The renderer no longer erases after a scroll. The scroll operation also adds an erase operation. This also means that erase operation are subject to adjustments by later scroll operations.
2019-06-25 20:11:08 +02:00
struct grid *grid, enum damage_type damage_type,
struct scroll_region region, int lines);
Use a 'damage' list to communicate what needs to be updated Instead of having each cell in the grid track it's own dirtiness, grid operations now append "damage" to a list. This list is consumed every time we render the grid. This allows us to special case some operations, like erase (and in the future, scroll).
2019-06-19 14:17:43 +02:00
wip: vt parsing: break out grid operating functions
2019-06-17 19:33:10 +02:00
void grid_erase(struct grid *grid, int start, int end);
grid: track both linear and row,col cursor
2019-06-17 21:15:20 +02:00
void grid_cursor_to(struct grid *grid, int row, int col);
void grid_cursor_left(struct grid *grid, int count);
void grid_cursor_right(struct grid *grid, int count);
wip: initial input handling
2019-06-19 10:04:47 +02:00
void grid_cursor_up(struct grid *grid, int count);
void grid_cursor_down(struct grid *grid, int count);
grid: track both linear and row,col cursor
2019-06-17 21:15:20 +02:00
wip: initial scrolling support (no scrollback though)
2019-06-19 10:27:31 +02:00
void grid_scroll(struct grid *grid, int rows);
vt: implement reverse scrolling (terminfo 'ri') This currently duplicates the code paths for DAMAGE_SCROLL; there are many similarities between the two, but also major differences...
2019-06-23 17:16:52 +02:00
void grid_scroll_reverse(struct grid *grid, int rows);
wip: initial scrolling support (no scrollback though)
2019-06-19 10:27:31 +02:00
scroll-region: don't clear damage queue when changing scroll region Vim, for example, changes the scroll region every time you scroll a single line. Thus, resetting the damage queue is slow. This reworks the damage handling of scroll updates: * Split damage queue into two: one for scroll operations and one for update/erase operations. * Don't separate update/erase operations inside/outside the scroll region * Store the current scroll region in the scroll damage operation. This allows us to stack multiple scroll operations with different scroll regions. * When updating update/erase operations after a scroll operation, split the update/erase operations if necessary (the current scroll operation may have a scroll region different from before, thus forcing us to split existing update/erase operations. * The renderer no longer erases after a scroll. The scroll operation also adds an erase operation. This also means that erase operation are subject to adjustments by later scroll operations.
2019-06-25 20:11:08 +02:00
void grid_scroll_partial(
struct grid *grid, struct scroll_region region, int rows);
void grid_scroll_reverse_partial(
struct grid *grid, struct scroll_region region, int rows);
scrolling region: wip
2019-06-23 21:12:32 +02:00
grid: track both linear and row,col cursor
2019-06-17 21:15:20 +02:00
int grid_cursor_linear(const struct grid *grid, int row, int col);
wip: initial scrolling support (no scrollback though)
2019-06-19 10:27:31 +02:00
grid: track both linear and row,col cursor
2019-06-17 21:15:20 +02:00
//void grid_cursor_to(struct grid *grid, int pos);
//void grid_cursor_move(struct grid *grid, int cols);
Reference in a new issue Copy permalink