Options
Refreshing the data for Recent/Frequent and Drives menus in a separate process
- Refreshing the data for Recent/Frequent and Drives menus in a separate process
-
Refreshing the data for Recent/Frequent and Drives menus in a separate process
LaurentG > 2020-11-11 06:25
(2020-11-10 16:44)Jean Lalonde Wrote: The thread refreshing the menu and the background thread that refreshes the database are different threads. But, as explained in the AHK doc, it is not truly a multithreaded environment:
Maybe (...?) an approach could be to have two completely distinct processes.
A new independent process would be in charge of refreshing the menu, and updates the DB could, generating a file with all menu entries (inc. live folders sub levels, inc. frequent and recent, inc. Disks list)
And the "main" QAP would have "only" to get these lists (readig the files generated by the other process) but being freed of task to elaborate them.... -
Refreshing the data for Recent/Frequent and Drives menus in a separate process
Jean Lalonde > 2020-11-11 07:32
(this is a spin-off from a discussion started about QAP beta release) -
RE: Refreshing the data for Recent/Frequent and Drives menus in a separate process
joeNOR > 2020-11-13 09:16
I'm gonna chime in here even if I am "the great naysayer" on this forum, and mr. Negative himself!
Since AHK/QAP is not true multi threading.
Create a helper tool, rebuild QAPmessenger to be QAPhelper containing the previous functions from QAPmessenger and an interface for tasks and new features.
(Optionally keep a stub called QAPmessenger that calls QAPhelper to be backward compatible).
Let it be optional for those users that prefer the installer version of QAP to let the QAPhelper run as a scheduled task in Windows.
For us preferring the portable version, call QAPhelper from QAP (configurable in the settings).
My two cent....
Regards,
joeNOR