Search found 3 matches
- Thu Oct 26, 2017 9:28 am
- Forum: Windows Discussion Forum
- Topic: Add <ExecutableName> via the SDK
- Replies: 5
- Views: 3183
Re: Add <ExecutableName> via the SDK
Indeed, that is what we assumed, unfortunately the driver then continues to use that default config rather than re-loading the existing My-App config after SiOpen. If the user then changes their settings again (which they instantly do because everything feels wrong) then the old config is overwritte...
- Wed Oct 25, 2017 9:23 am
- Forum: Windows Discussion Forum
- Topic: Add <ExecutableName> via the SDK
- Replies: 5
- Views: 3183
Re: Add <ExecutableName> via the SDK
Thanks for the quick reply. We are currently only using the default file, our application just handles events, doesn't manage any of the properties. It is the config in %APPDATA% that we tried manually editing to add the ExecutableName and that solved the issue with the profiles being overwritten. B...
- Wed Oct 25, 2017 3:44 am
- Forum: Windows Discussion Forum
- Topic: Add <ExecutableName> via the SDK
- Replies: 5
- Views: 3183
Add <ExecutableName> via the SDK
Hi all. We have an issue where profiles are lost between versions of the software. We have different versions of the software, each with a version number at the end of the executable name (e.g. MyProg21.exe, MyProg22.exe) and we feed SiOpen the app name MyProg. The issue with the profiles being lost...