Jean Lalonde > 2020-11-03 08:57
Jean Lalonde > 2020-11-06 17:27
joeNOR > 2020-11-08 04:50
Jean Lalonde > 2020-11-08 08:32
joeNOR > 2020-11-08 10:18
C:\Configs\QAP\QuickAccessPopup-64-bit.exe /Settings:C:\Configs\INI-files\QAP-%computername%.ini
Jean Lalonde > 2020-11-08 11:35
(2020-11-08 10:18)joeNOR Wrote: Observations v.11.0.6.9.2 Beta
Version: QAP v.11.0.6.9.2 x64 Portable
File Manager: Directory Opus v.12.22 Pro x64 ("DOpus") and Windows 10 File Explorer ("Explorer")
OS: Windows 10 Pro x64 2004, Server 2016 Core, Server 2019 Core.
Observation, possible bug?
Customize --> File --> "Open QAP Settings Folder"
This menu choice seems not to work when QAP use an INI file outside the QAP folder.
Example:
With DOpus it just goes to C:\.Code:C:\Configs\QAP\QuickAccessPopup-64-bit.exe /Settings:C:\Configs\INI-files\QAP-%computername%.ini
With Explorer it goes to the folder where the QAP exe is (C:\Configs\QAP\ in the example above), so the menu text is maybe a little ambiguous?
Same behaviour with v.11.0.5 and v.11.0.6.1 so this is not a (possible) bug with this beta only.
Jean Lalonde > 2020-11-08 12:20
joeNOR > 2020-11-08 12:21
Jean Lalonde > 2020-11-08 15:56
Jean Lalonde > 2020-11-08 15:58
joeNOR > 2020-11-08 17:43
Jean Lalonde > 2020-11-08 18:39
joeNOR > 2020-11-09 00:08
LaurentG > 2020-11-09 03:41
(2020-11-09 00:08)joeNOR Wrote: Consider this thought experiment:
Remove the checkbox and let the exclusion list be the only way to tell QAP to ignore certain letters.
(This is a list purely to insulate QAP from drives going offline, the only "protection" is QAP protecting itself )
Fill that list or clear it, and the practical effect will be exactly the same.
joeNOR > 2020-11-09 03:51
Jean Lalonde > 2020-11-09 08:55
joeNOR > 2020-11-09 09:05
Jean Lalonde > 2020-11-09 10:17
Jean Lalonde > 2020-11-09 13:40
joeNOR > 2020-11-10 12:11
Jean Lalonde > 2020-11-10 12:31
joeNOR > 2020-11-10 14:00
LaurentG > 2020-11-10 15:26
Jean Lalonde > 2020-11-10 16:44
Quote:Although AutoHotkey doesn't actually use multiple threads, it simulates some of that behavior: If a second thread is started -- such as by pressing another hotkey while the previous is still running -- the current thread will be interrupted (temporarily halted) to allow the new thread to become current.https://www.autohotkey.com/docs/misc/Threads.htm
Jean Lalonde > 2020-11-11 07:33
(2020-11-11 06:25)LaurentG Wrote:(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....