PR5/PR7: When to introduce QSortFilterProxyModel for grid + filmstrip sync #15
Labels
No labels
Kind/Bug
Kind/Feature
Priority/High
Priority/Medium
Reviewed/Confirmed
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ai-collab/bulk-image-organizer#15
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
DESIGN.md places
QSortFilterProxyModelfilter logic in PR8, but PR7 requires a bottom filmstrip sharing the same model/proxy and synced selection with the main grid.Ambiguity
MainWindow?Options
ImageSortFilterProxyModelsubclass with default accept-all; grid + future filmstrip both use proxy.Requested decision
Pick option + note whether scan-time incremental inserts require
invalidateFilter/sortpolicies.Blocks
Non-blocking for PR5; should be decided before PR7 filmstrip wiring.
Resolved per ValleyGeek comment — recorded as DR-014 in
docs/DECISIONS.mdand DESIGN.md PR7/PR4.Decision summary:
ImageListModelthrough PR5–6; introduceQSortFilterProxyModelin PR7 with filmstripPR5: complete with direct model (no proxy).
Follow-up: new issue #17 tracks metadata-scan sort implementation (not PR5 scope).
Closing as resolved.