FileSieve 4

  • Status Assigned
  • Percent Complete
  • Task Type Bug Report (major)
  • Category Backend / Core
  • Assigned To
    Joseph Cox
  • Operating System All
  • Severity High
  • Priority High
  • Reported Version 4.00
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: FileSieve 4
Opened by Joseph Cox - 21 November 2016

FS#24 - No processed items prevents BeginInvoke from working

Example: Classification Method not finding any matches if no items are processed.

The problem appears to be related to there being items to be processed, but they have all been set to Item.IsProcessed = False. This means that no items have been processed, which seems to cause a problem with the Windows Taskbar progress indicator.

Fixing this will have to be an ongoing process; in the meantime, EnableTaskbarProgress has been added to Settings - Advanced and should be set to False should the issue of the FileSieve window staying disabled after processing has completed.

Joseph Cox commented on 21 November 2016 02:28 PM

The Free Edition does not appear to have this problem.


Available keyboard shortcuts


Task Details

Task Editing