1
0
Fork 0
mirror of https://github.com/maziggy/bambuddy.git synced 2026-05-09 08:25:54 +02:00

[GH-ISSUE #397] [Feature]: Group duplicate prints in archive, improve history UX #249

Closed
opened 2026-05-07 00:08:04 +02:00 by BreizhHardware · 0 comments

Originally created by @Keybored02 on GitHub (Feb 16, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/397

Originally assigned to: @Keybored02 on GitHub.

Problem or Use Case

I am not really into the archive's way of showing multiple prints of the same object. It's hard to distinguish similar objects, it doesn't tell how many time each has been printed at a glance, it easily clutters the UI. I really like Mainsail's way of showing history.

Dev will start with 0.2.1b.

Proposed Solution

Wishlist:

  • Add a group filter that compacts duplicates prints of the same object together in Archive grid/list view. Tis setting persists sessions
  • Add a counter of times printed (like in the file manager) and a status indicator of the last print (successful/cancelled) to at least the Archive list view
  • Add dropdown menu on click in list view to show all grouped? Idk, there's not much sense in keeping full duplicates if the info that changes is very little, and not that relevant. Might be useful for future features though
  • Fit more info in list view, both for Archives and File, by compressing height of listings
  • Add customizable UI columns to let the user choose which metadata to show in Archive list view, and possibly File manager list view
  • Fit all of the above to work with incoming Archive log view
  • Improve selection with bigger click areas, area selections

Alternatives Considered

No response

Feature Category

Print Archiving

Priority

Would improve my workflow

Mockups or Examples

Image Image

Contribution

  • I would be willing to help implement this feature

Checklist

  • I have searched existing issues to ensure this feature hasn't already been requested
Originally created by @Keybored02 on GitHub (Feb 16, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/397 Originally assigned to: @Keybored02 on GitHub. ### Problem or Use Case I am not really into the archive's way of showing multiple prints of the same object. It's hard to distinguish similar objects, it doesn't tell how many time each has been printed at a glance, it easily clutters the UI. I really like Mainsail's way of showing history. Dev will start with 0.2.1b. ### Proposed Solution Wishlist: - [x] Add a group filter that compacts duplicates prints of the same object together in Archive grid/list view. Tis setting persists sessions - [x] Add a counter of times printed (like in the file manager) and a status indicator of the last print (successful/cancelled) to at least the Archive list view - [x] Add dropdown menu on click in list view to show all grouped? _Idk, there's not much sense in keeping full duplicates if the info that changes is very little, and not that relevant. Might be useful for future features though_ - [ ] Fit more info in list view, both for Archives and File, by compressing height of listings - [ ] Add customizable UI columns to let the user choose which metadata to show in Archive list view, and possibly File manager list view - [ ] Fit all of the above to work with incoming Archive log view - [ ] Improve selection with bigger click areas, area selections ### Alternatives Considered _No response_ ### Feature Category Print Archiving ### Priority Would improve my workflow ### Mockups or Examples <img width="1636" height="937" alt="Image" src="https://github.com/user-attachments/assets/fa53b648-7409-4195-86e6-6cbfbc81f927" /> <img width="1626" height="873" alt="Image" src="https://github.com/user-attachments/assets/a04d1e6c-ffc5-4829-8b52-7ad064c3deda" /> ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested
BreizhHardware 2026-05-07 00:08:04 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/bambuddy-maziggy-1#249
No description provided.