FileSieve 4

  • Status New
  • Percent Complete
    90%
  • Task Type Feature
  • Category Backend / Core
  • Assigned To
    Joseph Cox
  • Operating System All
  • Severity Low
  • Priority Low
  • Reported Version 4.09
  • Due in Version 4.32
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: FileSieve 4
Opened by Joseph Cox - 26 December 2016
Last edited by Joseph Cox - 19 November 2017

FS#178 - Allow adding profiles to the Windows Explorer context menu

Allow the user to add specific profiles to the Windows Explorer right-click shell context menu so profiles can be quickly run on a directory.

“Shell codes” (eg. %shell_file1%) will need to be added in various parts of FileSieve so Explorer folders/files can be referenced and acted upon.

Admin
Joseph Cox commented on 10 November 2017 03:05 PM

Began work on a project (that’s part of the FileSieve Solution) called FileSieve.Launcher.

After some thought, I’ve decided that FileSieve should only add a single item entry to the Windows Explorer shell; due to testing a number of years back, having a cascading context menu requires writing a .dll that is called every time the user opens the context menu. I really, really don’t like the idea of having a DLL that’s referenced each time.

Because of this, I’m going with having a single item - which doesn’t require a .dll and is simply an entry within the system’s registry - that opens the FileSieve Launcher. This will allow a large amount of flexibility.

The downside is that FileSieve.Launcher.exe is invoked when the menu item is selected; this can cause a delay of a second or two before the window appears on (much) slower systems.

Admin
Joseph Cox commented on 10 November 2017 08:29 PM

I’ve gone with a Metro-style form for the launcher.

Windows Explorer Shell integration is now in and settable via Settings - Interface in FileSieve. “In” and in it appears within the shell’s context menu; the Launcher side of things isn’t complete as of yet.

Admin
Joseph Cox commented on 16 November 2017 08:24 AM

Having second thoughts about the Metro-style interface...

Admin
Joseph Cox commented on 16 November 2017 08:57 PM

Reshuffled the Metro-style interface and it looks better. Think I'll stick with it for now.

Haven't implemented any of the %shell_file1% stuff mentioned in the task description as it doesn't seem to be needed. The Automation support added previously appears to have taken care of all of that, although I did need to add /clearsources and /sources parameters.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing