Zhuzi > 2025-09-11 15:38
Jean Lalonde > 2025-09-11 15:50
Zhuzi > 2025-09-11 23:56
Jean Lalonde > 2025-09-12 09:37
Xavier > 2025-09-14 23:29
AddObsidianLinkToQAP:
global qapfavname := ""
global OBQAPTitle := ""
WinActivate, ahk_exe Obsidian.exe
sleep 100
WinGetTitle, OBQAPTitle, A ;ahk_exe Obsidian.exe
global qapfavname := RegExReplace(OBQAPTitle, "- Obsidian.*", "")
; MsgBox %qapfavname%`n`n%OBTitle%
sendinput, ^+{U}
sleep 100
gosub qapADDURL
sleep 200
sendinput, ^{pgdn}
sleep 500
CoordMode, mouse, window
click, 66, 311
WinWaitActive, Select Icon - Quick ahk_class JeanLalonde.ca, File name:,5
sleep 500
click, 493, 60 ; controlclick, Button1 ,Select Icon - Quick, Browse,left,1
sleep 200
sendinput, ^a
sleep 100
sendinput, ^a
sleep 100
sendinput, ^a
sleep 100
sendraw, %obsidian%
sleep 300
sendinput {enter}
sleep 300
sendinput {enter}
return if RegExMatch(Clipboard, "i)^obsidian://") ; obsidian uri
{
menu, c, add, Save Obsidian URL to QAP (Clip), AddObsidianLinkToQAPCLIPPED
menu, c, icon, Save Obsidian URL to QAP (Clip), %icons%\QAPaddstar+.ico,,%is%
Menu, c, add, Save Obsidian URI.url (Clip), SaveLocalURIURLclip
Menu, c, Icon, Save Obsidian URI.url (Clip), %icons%\obsidiansave.ico,,%is%
}
AddOneNoteLinkToQAPCLIPPED:
AddObsidianLinkToQAPCLIPPED:
qapADDURL:
{
DetectHiddenWindows, On
CoordMode, mouse, window
if WinExist("Customize - Quick Access Popup ahk_class JeanLalonde.ca")
{
WinMenuSelectItem, Customize - Quick Access Popup ahk_class JeanLalonde.ca,,Favorite, Add
sleep 300
WinWaitActive, Add Favorite Type - Quick Access Popup ahk_class JeanLalonde.ca
sleep 200
sendinput, {l}
sleep 90
sendinput, {enter}
sleep 150
WinWaitActive, Add Favorite: Link (URL) - Quick Access Popup ahk_class JeanLalonde.ca
sleep 150
if (qapfavname != "")
{
ControlSetText, Edit1, %qapfavname%, Add Favorite: Link (URL) -, Favorite Type: Link (URL)
sleep 150
}
ControlSetText, Edit2, %Clipboard%, Add Favorite: Link (URL) -, Favorite Type: Link (URL)
sleep 150
}
}
global qapfavname := ""
global OBQAPTitle := ""
returnJean Lalonde > 2025-09-16 07:18
Jean Lalonde > 2025-09-28 21:01
Zhuzi > 2025-09-30 16:36
(2025-09-28 21:01)Jean Lalonde Wrote: In v11.6.7, Directory Opus collections (coll:\\) are now supported.
See https://forum.quickaccesspopup.com/showt...p?tid=3080
Jean Lalonde > 2025-10-02 13:45
Zhuzi > 2025-10-03 22:01
(2025-10-02 13:45)Jean Lalonde Wrote: > However, the options of live folder is not actually working. I have enabled it.
I'm not sure how easy/hard il would be to implement Live folders for DOpus collections. What do you have in mind?
Jean Lalonde > 2025-10-05 09:58
Zhuzi > 2025-11-25 15:34
Jean Lalonde > 2025-11-25 16:02
Quote:Directory Opus stores its collections as XML files with a .col extension. These files act as "virtual folders," containing only the paths (references) to the actual files, not the files themselves.
Here is a breakdown of exactly how and where they are saved:
1. Physical File Location
Directory Opus saves your collections in the specific Collections folder within your user profile's AppData directory.
Path: %AppData%\GPSoftware\Directory Opus\Collections (You can paste this path directly into the Directory Opus address bar or Windows Explorer to open it.)
2. File Format (.col)
Each top-level collection you create appears in this folder as a separate file with the .col extension (e.g., MyWork.col).
Format: Despite the custom extension, the file content is standard XML.
Editing: You can open these .col files with any text editor (like Notepad or VS Code) to view the raw data.
3. Internal Structure
Inside the .col file, Opus uses a simple XML structure to list the referenced files. It typically looks like this:
XML
<?xml version="1.0" encoding="UTF-8"?>
<collection name="My Collection">
<item>D:\Photos\Image1.jpg</item>
<item>C:\Work\Documents\Report.pdf</item>
</collection>
Nested Collections: If you create a sub-collection (a folder inside a collection), Opus creates a physical folder in the %AppData% directory matching the parent collection's name, and places the new .col file inside that folder.
4. Important "Save" Behavior
Directory Opus does not always write changes to the .col file on disk immediately after you drag a file into a collection.
Trigger: The physical .col file is usually updated/saved when you navigate away from the collection folder or close the specific window (Lister).
Implication: If you are trying to read this file programmatically (e.g., with a script), ensure you have navigated out of the collection in the Opus interface first to ensure the latest changes have been flushed to disk.
5. Accessing via Commands
Internally, Opus refers to these locations using the coll:// protocol rather than the physical C:\... path.
Example: coll://Find Results or coll://MyWork
Automation: If you need to export a collection to a text file without parsing the XML yourself, you can use the built-in dopusrt.exe command line helper: dopusrt.exe /col export "My Collection" "C:\Output\List.txt"