new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Tauri · Plugins and security · all subjects

deep-link/runtime

3 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Register desktop deep links at runtime

On Linux and Windows, you can register deep link schemes at runtime using the app.deep_link().register("scheme-name") Rust function. This can be useful for development when the app is not installed.

Register all deep links at runtime

You can register all statically configured deep links at runtime using app.deep_link().register_all(). This is useful for development on Linux and Windows as it ensures the deep links are registered without requiring app installation. Call within a cfg block for target_os = "linux" or for debug_assertions on windows.

Register desktop deep links at runtime - example

Example code for registering a scheme at runtime in Rust: use tauri_plugin_deep_link::DeepLinkExt; #[cfg_attr(mobile, tauri::mobile_entry_point)] pub fn run() { tauri::Builder::default() .plugin(tauri_plugin_deep_link::init()) .setup(|app| { #[cfg(desktop)] app.deep_link().register("my-app")? Ok(()) }) .run(tauri::generate_context!()) .expect("error while running tauri application"); }

Give your agent this brain