From edab9a62ad361eeff8bb9d1aa30aea1ee4f1c536 Mon Sep 17 00:00:00 2001 From: nova Date: Tue, 23 Jun 2026 21:42:10 +0200 Subject: [PATCH] faster initial render --- main.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/main.c b/main.c index 1da42a1..7c92aff 100644 --- a/main.c +++ b/main.c @@ -18,7 +18,7 @@ unsigned int terminal_width; unsigned int temp_heigth = 0; /*used for screen refresh*/ unsigned int temp_width = 0; unsigned int file_modifiers = 0; -unsigned int status = (STATUS_RUN_BACKEND | STATUS_UPDATE_SCREEN_CLEAR | STATUS_UPDATE_SCREEN_RESIZE | STATUS_RELOAD_DIRECTORY) & ~STATUS_UPDATE_SCREEN_RESIZE; +unsigned int status = (STATUS_RUN_BACKEND | STATUS_UPDATE_SCREEN_CLEAR | STATUS_UPDATE_SCREEN_RESIZE | STATUS_RELOAD_DIRECTORY); char *global_path; time_t seed; @@ -75,6 +75,14 @@ int main(){ timeout(SETTINGS_CURSES_TIMEOUT); + /* initial render pass to speed first render up, + * yes this only skips SETTINGS_CURSES_TIMEOUT, which by default is 100ms, + * but i started to write th out of spite; because anything else either is too slow and unresponsive + * or i just dont like their ux. + * will i ever make use of the 100ms? will i ever react and do faster inputs? no + * does it feel more responsive? sure does */ + pthread_cond_signal(&cond_mid); + render_pass(); while(!(status & STATUS_QUIT_PROGRAM)){ getmaxyx(stdscr, terminal_height, terminal_width);