PDF Explorer > Bug reports

WorkGrid/ScanGrid sync issue


there's a trick: if you "Copy selected files from grid to grid" while in ScanGrid, and edit that file entry with Quick Info Fields Edit tool while in WorkGrid, you will get Info Field updated in WorkGrid but in ScanGrid it will stay unchanged. If you would press "Copy selected files from grid to grid" again while in WorkGrid then the entry that is in the ScanGrid would not get updated/changed. Also, if you have some entry already set, and copy the entry to the WorkGrid, edit it there, then get back to the ScanGrid, and make for example the value blank (pretending you forgot about the previous edit), you have no way to update the WorkGrid value (without removing it and copying back again). On the other hand, the only way to update ScanGrid value (from WorkGrid value changes) is to refresh the DiskTree tool, which in turn re-enlists all the entries you have already removed from the ScanGrid list, or in other words - destroys the list. It seems that after app restart you get the last modified field value as it's what is stored in the file metadata itself.
I see it as a bug because you can easily get lost in a sea of entries and re-edit something that was edited, or simply lose track of where was the last change was made, or if the file gets moved... etc.
Maybe it is reasonable to make (1) entry font in italic if it has been copied to WorkGrid and (2) to create a button "Sync WorkGrid and ScanGrid" so that it would update field entries with latest changes and (3) make italics for ScanGrid all entries found in WorkGrid?


It is a known issue. The grids act independently of each other with the items not maintaining a link when they are copied to the other grid. The copy operation also just check if the file is already referenced in the other grid, not updating its fields if already present. No idea right now if updating the fields in this situation is desirable .
The manual sync functionality you propose is probably the way to go.

I think unchanged entry creates a possibility for ambiguous situations - and it is always undesirable while working with data. It should be left for the user to verify that these situations do not arise with a separate sync button (and a hotkey), at least.


[0] Message Index


Go to full version