You are talking about the menu option File->Save Configuration... which is incomplete. The configuration is saved automatically when closing the program, and restored at program startup. In that case, the extra controllers are saved correctly. If you prefer your own configuration file name and location, you may use the command line -f, --file for that purpose as a workaround.
The normal configuration file name and location in Linux is: $HOME/.config/vmpk.sourceforge.net/VMPK.conf
The flatpak version uses another location: $HOME/.var/app/net.sourceforge.VMPK/config/vmpk.sourceforge.net/VMPK.conf
To run the Flatpak version with a custom configuration file name, the invocation may be: $ flatpak run net.sourceforge.VMPK --file ~/custom_vmpk.conf
this will save and restore automatically the configuration from the given file.
Ticket moved from /p/vmpk/feature-requests/77/
You are talking about the menu option File->Save Configuration... which is incomplete. The configuration is saved automatically when closing the program, and restored at program startup. In that case, the extra controllers are saved correctly. If you prefer your own configuration file name and location, you may use the command line
-f, --filefor that purpose as a workaround.The normal configuration file name and location in Linux is:
$HOME/.config/vmpk.sourceforge.net/VMPK.confThe flatpak version uses another location:
$HOME/.var/app/net.sourceforge.VMPK/config/vmpk.sourceforge.net/VMPK.confTo run the Flatpak version with a custom configuration file name, the invocation may be:
$ flatpak run net.sourceforge.VMPK --file ~/custom_vmpk.confthis will save and restore automatically the configuration from the given file.
The AppImage binary has its own complementary mechanism:
https://docs.appimage.org/user-guide/portable-mode.html
GitHub ticket 18