[GH-ISSUE #259] Feature: Add Save config from GTK frontend #128

New issue

Open

opened 2026-05-05 22:10:38 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 22:10:38 -06:00

Owner

Originally created by @markmandel on GitHub (Feb 8, 2025).
Original GitHub issue: https://github.com/feschber/lan-mouse/issues/259

Just a nice to have feature, especially for those people who aren't as comfortable writing config files.

Once you have a config working in the GTK application, have a "save" or "export" button to save that to the appropriate place locally ($XDG_CONFIG_HOME/lan-mouse/config.toml since I'm on Linux).

Makes it easy to experiment with the gtk frontend first, get everything working, and then persist it for future sessions without having to type it all out.

Originally created by @markmandel on GitHub (Feb 8, 2025). Original GitHub issue: https://github.com/feschber/lan-mouse/issues/259 Just a nice to have feature, especially for those people who aren't as comfortable writing config files. Once you have a config working in the GTK application, have a "save" or "export" button to save that to the appropriate place locally (`$XDG_CONFIG_HOME/lan-mouse/config.toml` since I'm on Linux). Makes it easy to experiment with the gtk frontend first, get everything working, and then persist it for future sessions without having to type it all out.

gitea-mirror commented

2026-05-05 22:10:40 -06:00

Author

Owner

@feschber commented on GitHub (Feb 12, 2025):

Yeah I have already started to work on this because the encryption stuff is fairly unusable otherwise.

@feschber commented on GitHub (Feb 12, 2025): Yeah I have already started to work on this because the encryption stuff is fairly unusable otherwise.

gitea-mirror commented

2026-05-05 22:10:40 -06:00

Author

Owner

@feschber commented on GitHub (Feb 7, 2026):

I've now opted to autosave upon configuration changes with #345.

For now, this will override the config file each time, however my plan going forward is to make it so that clients configured through the config file are permanent / immutable, while clients configured through the UI / frontend are saved to $XDG_DATA_HOME instead.

@feschber commented on GitHub (Feb 7, 2026): I've now opted to autosave upon configuration changes with #345. For now, this will override the config file each time, however my plan going forward is to make it so that clients configured through the config file are permanent / immutable, while clients configured through the UI / frontend are saved to `$XDG_DATA_HOME` instead.

gitea-mirror commented

2026-05-05 22:10:42 -06:00

Author

Owner

@myInstagramAlternative commented on GitHub (Feb 8, 2026):

Hey @feschber, thanks for the app. I was able to build dev (from source) on MacOs (arm) and on Asahi Fedora Hyprland(aarm64). CMD, option and control passtrough work from MacOS to Hyprland.

I don't want to open new issue for this, since there is probably a duplicate somewhere or you are well aware of this - I just want to point out that application crashes when I try to add connection or authorize incoming connection if ~/.config/lan-mouse/config.toml is not present.

thread 'main' (33668) panicked at src/config.rs:438:14:
config
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

@myInstagramAlternative commented on GitHub (Feb 8, 2026): Hey @feschber, thanks for the app. I was able to build dev (from source) on MacOs (arm) and on Asahi Fedora Hyprland(aarm64). CMD, option and control passtrough work from MacOS to Hyprland. I don't want to open new issue for this, since there is probably a duplicate somewhere or you are well aware of this - I just want to point out that application crashes when I try to add connection or authorize incoming connection if ~/.config/lan-mouse/config.toml is not present. thread 'main' (33668) panicked at src/config.rs:438:14: config note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

gitea-mirror commented

2026-05-05 22:10:43 -06:00

Author

Owner

@feschber commented on GitHub (Feb 8, 2026):

@myInstagramAlternative thanks for letting me know, should be fixed!

@feschber commented on GitHub (Feb 8, 2026): @myInstagramAlternative thanks for letting me know, should be fixed!