pub trait HasMvGetFunctions:
HasHandle<WINDOW>
+ HasYXAxis
+ HasNonBlocking {
// Provided methods
fn mvgetch(
&self,
origin: Origin,
) -> Result<CharacterResult<char>, NCurseswWinError> { ... }
fn mvgetnstr(
&self,
origin: Origin,
length: u16,
) -> Result<String, NCurseswWinError> { ... }
fn mvgetn_wstr(
&self,
origin: Origin,
length: u16,
) -> Result<WideString, NCurseswWinError> { ... }
fn mvgetstr(&self, origin: Origin) -> Result<String, NCurseswWinError> { ... }
fn mvget_wch(
&self,
origin: Origin,
) -> Result<CharacterResult<WideChar>, NCurseswWinError> { ... }
fn mvget_wstr(&self, origin: Origin) -> Result<WideString, NCurseswWinError> { ... }
fn mvgetch_nonblocking(
&self,
origin: Origin,
timeout: Timeout,
) -> Result<NonBlockingResult<char>, NCurseswWinError> { ... }
fn mvget_wch_nonblocking(
&self,
origin: Origin,
timeout: Timeout,
) -> Result<NonBlockingResult<WideChar>, NCurseswWinError> { ... }
}
Expand description
Does the window canvas type have ncursesw get origin functions.
Provided Methods§
fn mvgetch( &self, origin: Origin, ) -> Result<CharacterResult<char>, NCurseswWinError>
fn mvgetnstr( &self, origin: Origin, length: u16, ) -> Result<String, NCurseswWinError>
fn mvgetn_wstr( &self, origin: Origin, length: u16, ) -> Result<WideString, NCurseswWinError>
fn mvgetstr(&self, origin: Origin) -> Result<String, NCurseswWinError>
👎Deprecated since 0.1.1: underlying native function can cause issues. Use mvgetnstr() instead
fn mvget_wch( &self, origin: Origin, ) -> Result<CharacterResult<WideChar>, NCurseswWinError>
fn mvget_wstr(&self, origin: Origin) -> Result<WideString, NCurseswWinError>
👎Deprecated since 0.1.1: underlying native function can cause issues. Use mvgetn_wstr() instead
fn mvgetch_nonblocking( &self, origin: Origin, timeout: Timeout, ) -> Result<NonBlockingResult<char>, NCurseswWinError>
fn mvget_wch_nonblocking( &self, origin: Origin, timeout: Timeout, ) -> Result<NonBlockingResult<WideChar>, NCurseswWinError>
Dyn Compatibility§
This trait is not dyn compatible.
In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.