View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000022||FileSieve||Backend / Core||public||2018-10-05 23:04||2020-04-19 15:59|
|Target Version||4.55||Fixed in Version||4.55|
|Summary||0000022: 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.
Not sure if this is the same sorta thing, but changing
Quick addition: It didn't seem to matter (this time?) whether any files were processed or not; it just seemed random if the invokes would work.
|2018-10-05 23:04||BootBlock||New Issue|
|2018-10-05 23:04||BootBlock||Status||new => assigned|
|2018-10-05 23:04||BootBlock||Assigned To||=> BootBlock|
|2018-10-05 23:04||BootBlock||Tag Attached: Processing|
|2020-04-17 23:42||BootBlock||Note Added: 0000261|
|2020-04-19 15:58||BootBlock||Note Added: 0000262|
|2020-04-19 15:58||BootBlock||Status||assigned => resolved|
|2020-04-19 15:58||BootBlock||Resolution||open => fixed|
|2020-04-19 15:58||BootBlock||Fixed in Version||=> 4.55|
|2020-04-19 15:58||BootBlock||Target Version||=> 4.55|
|2020-04-19 15:59||BootBlock||Note Added: 0000263|