#cursor-position #ratatui #cursor #input

rat-cursor

ratatui trait to communicate the cursor position across widgets

3 unstable releases

0.25.1 Oct 18, 2024
0.25.0 Oct 8, 2024
0.1.0 Sep 12, 2024

#1064 in Command-line interface

Download history 97/week @ 2024-09-09 32/week @ 2024-09-16 9/week @ 2024-09-23 13/week @ 2024-09-30 190/week @ 2024-10-07 232/week @ 2024-10-14 33/week @ 2024-10-21 27/week @ 2024-10-28

482 downloads per month
Used in 7 crates (3 directly)

MIT/Apache

5KB

crates.io Documentation License License

This crate is a part of rat-salsa.

Rat-Cursor

Why?

This crate defines just the trait HasScreenCursor for use in other crates. This aims to overcome the shortcomings of ratatui to handle cursor positioning by widgets.

In the long run I hope there will be a solution within ratatui which will make this obsolete, but for now ...

pub trait HasScreenCursor {
    fn screen_cursor(&self) -> Option<(u16, u16)>;
}

Use

Widget

This trait is implemented for the widget-state struct.

It's implemented for the state struct because the widget might need to run the full layout process to know the cursor position. Which would approximately double the rendering process.

Instead of setting the cursor position during rendering somehow, the rendering process stores the cursor position in the state struct, where it can be retrieved later on.

The trait returns a screen-position, but only if it actually needs the cursor to be displayed:

  • The cursor is not scrolled off-screen.
  • The widget has some kind of input-focus.

Container widget

A container widget can cascade down to its components.

    fn screen_cursor(&self) -> Option<(u16, u16)> {
    self.widget1.screen_cursor()
        .or(self.widget2.screen_cursor())
        .or(self.widget3.screen_cursor())
}

No runtime deps