Skip to content

Add copy details button to device error dialog - #11500

Open
BenJule wants to merge 1 commit into
bambulab:masterfrom
BenJule:feature/device-error-copy-details
Open

Add copy details button to device error dialog#11500
BenJule wants to merge 1 commit into
bambulab:masterfrom
BenJule:feature/device-error-copy-details

Conversation

@BenJule

@BenJule BenJule commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR adds a Copy Error Details button to DeviceErrorDialog.

Why

Printer/device error dialogs can contain useful troubleshooting details such as the error level, error code and message. Users often need to share those details in bug reports or support requests.

This PR makes that easier by adding a dedicated copy action for the currently displayed device error details.

Related to #11499

Implementation

  • Add a COPY_ERROR_DETAILS action button.
  • Store the currently displayed error title, error code text and error message.
  • Add Copy Error Details to the device error dialog button area.
  • Copy the stored details to the clipboard.
  • Return immediately after copying so the dialog stays open and no printer/device action is triggered.

Scope

This PR only affects DeviceErrorDialog.

It does not:

  • change printer error handling
  • change HMS/error lookup logic
  • change existing printer/device action buttons
  • affect the generic ErrorDialog
  • close the dialog after copying

Note

This is separate from the generic ErrorDialog copy button. DeviceErrorDialog is a custom printer/device error dialog and does not use the generic error dialog implementation.

Test plan

  • Trigger or instantiate a DeviceErrorDialog.
  • Confirm the dialog shows Copy Error Details.
  • Click Copy Error Details.
  • Confirm the visible error title/code/message are copied to the clipboard.
  • Confirm the dialog stays open after copying.
  • Confirm existing action buttons still work as before.

@Bambu-Pomfret

Copy link
Copy Markdown
Contributor

Hi @BenJule,

Could we avoid adding this new action to handle it? The action ID has to be kept consistent with firmware and Handy. If Studio reserves this ID now, it will limit the available IDs when firmware and Handy teams add new functionalities later on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants