Options
[Wishlist] True portability via reload option if INI changed elsewhere
- [Wishlist] True portability via reload option if INI changed elsewhere
-
[Wishlist] True portability via reload option if INI changed elsewhere
AlexHK > 2021-01-11 03:05
I know it's not recommended, but I am using the portable version of QAP on two computers concurrently and sync the files between them.
I need QAP on both with identical setup (favorites, settings, etc).
The reason why I do this is if I make changes to QAP (ie. add a new favorite or change settings), I want it on both computers.
I disabled a few things, such as the database, remembering window position, and specified a settings backup location in a subfolder which I then excluded from sync. It works for the moment and the worst thing that could happen is that I lose a change I made to the settings (which I could restore in worst case using the file history of the sync software).
I am the only user of the two systems but this still means QAP is open on both computers and the two instances may overwrite each others INI file in worst case or experience sync conflicts. I am the only user of the two systems, so that's not a biggie at the moment.
I read the knowledge base article and forum threads. I know! I am naughty.
However, I suggest to make QAP truly portable. Don't write back info (ie. window position) to the INI fil. Store this machine-related info which you currently write to the INI somewhere else, or don't store it if the window position is the only thing you need it for
Also, bonus points if you check during runtime if the INI file was changed since startup and and show us a message. So if we make changes to the settings on one computer or edit the INI via text editor (no matter on which machine) AQP says: the settings where changed or edited elsewhere, do you wish to reload QAP? yes/no. And even more bonus points if this message could be disabled via settings so either QAP or the INI file automatically (without user interaction) gets reloaded if it was changed.
At least for me, it's not expected that I make frequent QAP setting changes, at least not after the initial setting-up-and-getting-used-to-it phase. Other peoples workflow may vary, but this suggestion would cover all bases as far as I can tell.
Thanks for this amazing software Jean! No matter if you consider this for the future or not, I am glad I found it (I came via AHK forums). -
RE: [Wishlist] True portability via reload option if INI changed elsewhere
joeNOR > 2021-01-12 02:39
Hi!
The INI-file is also used for storing User Variables. They are unique for each machine.
You may want to have a look at Shared Menus, and optionally with User Variables.
I use this across 10+ machines running the portable version of QAP.
Triggering the shared menus with hotkeys makes the local INI not that important, except (in my case) when I have to add or change UserVars.
Regards,
joeNOR -
RE: [Wishlist] True portability via reload option if INI changed elsewhere
Jean Lalonde > 2021-01-12 11:35
> I know it's not recommended, but I am using the portable version of QAP on two computers concurrently and sync the files between them.
It is good to see that you've read the doc before making your suggestion :-)
> However, I suggest to make QAP truly portable. (...)
I appreciate your suggestions and could consider it for a new project. But these kind of changes it at this time would mean a lot of work, especially to manage the transition from the current architecture to the new one (backward compatibility, etc.).
As Joe suggested, you may find a convenient solution with Shared menus. Or, if you prefer, you could continue with your current approach as you are aware of its risks (sync conflicts, etc.) and understand how to handle them.
Thanks for your input Alex,
Jean