chore: fix new clippy warnings (derive default)

[hila-f-qodo]

Benchmark PR from qodo-benchmark#150

---

[devin-ai-integration]

Devin Review found 1 potential issue.

View issue and 4 additional flags in Devin Review.

[devin-ai-integration]

🔴 MouseButtonState mapping is inverted in From implementation

The From<tray_icon::MouseButtonState> implementation incorrectly inverts the mouse button state mapping, causing Up to be reported as Down and vice versa.

Click to expand

Mechanism

The conversion from tray_icon::MouseButtonState to Tauri's MouseButtonState has the mapping inverted:

match value {
  tray_icon::MouseButtonState::Up => MouseButtonState::Down,  // WRONG: should be Up
  tray_icon::MouseButtonState::Down => MouseButtonState::Up,  // WRONG: should be Down
}

Impact

When a user clicks on a tray icon:

• A mouse button press (Down from tray_icon) will be reported as Up to the application
• A mouse button release (Up from tray_icon) will be reported as Down to the application

This will break any application logic that depends on the correct mouse button state, such as:

• Detecting when a button is pressed vs released
• Implementing drag operations
• Distinguishing between click start and click end

Expected vs Actual

• Expected: tray_icon::MouseButtonState::Up → MouseButtonState::Up, tray_icon::MouseButtonState::Down → MouseButtonState::Down
• Actual: tray_icon::MouseButtonState::Up → MouseButtonState::Down, tray_icon::MouseButtonState::Down → MouseButtonState::Up

Recommendation: Fix the mapping to correctly convert the states:

match value {
  tray_icon::MouseButtonState::Up => MouseButtonState::Up,
  tray_icon::MouseButtonState::Down => MouseButtonState::Down,
}

---

Was this helpful? React with 👍 or 👎 to provide feedback.