Browse Source

Error messages don't actually get truncated, false alarm everybody

pull/162/head
Fenrir 10 months ago
parent
commit
9396939d64
  1. 7
      ctru-rs/src/applets/error.rs

7
ctru-rs/src/applets/error.rs

@ -55,8 +55,8 @@ impl PopUp {
/// ///
/// # Notes /// # Notes
/// ///
/// Messages that are too large will be truncated. The exact number of characters displayed can vary depending on factors such as /// The text will be converted to UTF-16 for display with the applet, and the message will be truncated if it exceeds
/// the length of individual words in the message and the chosen word wrap setting. /// 1900 UTF-16 code units in length after conversion.
#[doc(alias = "errorText")] #[doc(alias = "errorText")]
pub fn set_text(&mut self, text: &str) { pub fn set_text(&mut self, text: &str) {
for (idx, code_unit) in text for (idx, code_unit) in text
@ -105,9 +105,6 @@ impl PopUp {
/// # Notes /// # Notes
/// ///
/// * If the [`Gfx`] service is not initialized during a panic, the error applet will not be displayed and the old panic hook will be called. /// * If the [`Gfx`] service is not initialized during a panic, the error applet will not be displayed and the old panic hook will be called.
///
/// * As mentioned in [`PopUp::set_text`], the error applet can only display a finite number of characters and so panic messages that are too long
/// can potentially end up being truncated. Consider using this hook along with the default hook so that you can capture full panic messages via stderr.
pub fn set_panic_hook(call_old_hook: bool) { pub fn set_panic_hook(call_old_hook: bool) {
use crate::services::gfx::GFX_ACTIVE; use crate::services::gfx::GFX_ACTIVE;
use std::sync::TryLockError; use std::sync::TryLockError;

Loading…
Cancel
Save