Hmm I actually meant to post this in the context of the other thread (linked below), it probably makes more sense there (I had both open while researching the issue... that's what I get for posting while tired):
It might be a little out of place in this thread now, but I'll follow up since I started.
=========
In my case, I was trying to use middle-click events to execute a command/script (set up in File Type->Events), but the multi-select functionality was still in the way.
Or to generalize: The 'mandatory selection' behavior of any type of click can be in the way for some use-cases.
I did more research while writing this draft, and I just found a workaround to get mostly what I want. I ended up switching to using left-click instead of middle-click in this case, since it worked more smoothly with a selection caveat (mentioned below).
Workaround:
Result behavior: Ctrl + double-click a file to set it as 'focused' and 'deselected', then run a script against it. (Can also set up middle click for the same.)
I found this tip from an old post or yours, and was able to use the first part of the command to change the focused file while leaving the selections on other files.
So first, under File Type -> Events -> Left double-click + Ctrl, I can specify the command: Select DESELECT MAKEVISIBLE EXACT {file|noterm}
Then I can add a custom script command as part of the click event on newly-focused file, or run a separate hotkey script.
Example hotkey:
function OnClick(clickData)
{
DOpus.ClearOutput();
var cmd = clickData.func.command;
cmd.deselect = false; // Prevent automatic deselection
focused_item = clickData.func.sourcetab.GetFocusItem()
// <Perform commands with focused_item here>
}
The minor limitation is that if I'm targeting one of the files I had already selected, that file's selection will be cleared. However, since Ctrl + left single-click already toggles selection, it's not too flow-breaking to toggle back.