Hello,
I get an unexpected behavior with settings including :
workerconfig 4.5.1; filetypes { filetype { title = "Video"; pattern = ""; usepattern = false; usecontent = false; content { } type = normal; patternignorecase = false; patternuseregexp = false; patternusefullname = false; extcond = ""; useextcond = false; ftcommands { customaction { name = "view"; commands { OwnOp { separateeachentry = false; recursive = false; start = normal; com = "mpv --msg-level=all=no {F}"; viewstr = ""; inbackground = true; takedirs = false; dontcd = false; } } } } subtype { filetype { title = "AVI video"; pattern = "\\.\\(avi\\|divx\\|mp4\\)$"; usepattern = true; usecontent = false; content { } type = normal; patternignorecase = true; patternuseregexp = true; patternusefullname = false; extcond = ""; useextcond = false; ftcommands { } subtype { } colormode = default; unselectcolor = 1,0; selectcolor = 1,0; unselectactivecolor = 1,0; selectactivecolor = 1,0; } } colormode = default; unselectcolor = 1,0; selectcolor = 1,0; unselectactivecolor = 1,0; selectactivecolor = 1,0; } } buttons { button { position = 30; title = "voir"; color = 1,0; shortkeys { normal { key = "v"; } normal { key = "V"; } } commands { RunCustomAction { customname = "view"; } } } }
(of course, there are more subtypes and more commands, and several subtypes have their own ftcommands...)
When I right-click on a avi file, the context menu offers the "view" action and it woks fine: the customaction has been inherited by the "AVI video" subtype as I understand it. But when I click on the "voir" button, nothing appears.
If the "view" customaction is defined into the "AVI video" subtype, both context menu and button work as expected.
This seems to be specific of customaction : when I replace the customaction by a "user 0", everything is fine regardless of where (filetype or subtype) that "user 0" is defined.
Anyway... thank you very much for Worker ! It's been my only filemananger for years, and there is just nothing that compare to it.
Philippe
Hi,
thanks for the report, I can reproduce this issue and I will look into it.
I have fixed the issue in the current release 4.6.0.