feat: added Settings screen

[Vidhijain20]

Adds the Settings screen.

Screenshots / Recordings

Checklist:

• No hard coding: I have used resources from strings.xml, dimens.xml and colors.xml without hard coding any value.
• No end of file edits: No modifications done at end of resource files strings.xml, dimens.xml or colors.xml.
• Code reformatting: I have reformatted code and fixed indentation in every file included in this pull request.
• No extra space: My code does not contain any extra lines or extra spaces than the ones that are necessary.

Summary by Sourcery

Add a new Settings screen to allow users to toggle auto-start behavior and choose export data format, integrate it into the app’s navigation and provider logic.

New Features:

• Introduce SettingsScreen UI with a checkbox for auto-start and a list tile that opens a dialog to select TXT or CSV export format
• Register '/settings' route in main.dart and add a Settings entry in the navigation drawer

Enhancements:

• Extend BoardStateProvider with exportFormat and autoStart properties and conditionally subscribe to USB events based on autoStart
• Define new constants for settings labels and export formats in constants.dart
• Improve navigation drawer logic to correctly navigate to or reuse the Settings screen

[sourcery-ai]

Reviewer's Guide

This PR introduces a new Settings screen for configuring auto-start and export format options, integrates it into the app navigation, and extends the BoardStateProvider to persist these settings and conditionally manage USB auto-connect behavior.

Sequence Diagram for Conditional USB Auto-Connection

sequenceDiagram
    participant BSP as BoardStateProvider
    participant US as UsbSerial
    participant SCL as ScienceLabCommon

    BSP->>BSP: initialize()
    alt autoStart is true
        BSP->>US: usbEventStream.listen(...)
        US-->>BSP: UsbEvent.ACTION_USB_ATTACHED
        BSP->>BSP: attemptToConnectPSLab()
        BSP->>SCL: openDevice()
        SCL-->>BSP: pslabIsConnected = true
        BSP->>BSP: setPSLabVersionIDs()
    else autoStart is false
        BSP->>BSP: Skip UsbSerial event listening
    end

Loading

Sequence Diagram for Updating Settings

sequenceDiagram
    actor User
    participant SS as SettingsScreen
    participant BSP as BoardStateProvider

    User->>SS: Toggles "Auto Start" checkbox
    SS->>BSP: autoStart = (new value)
    BSP-->>SS: Notifies listeners (UI updates)

    User->>SS: Taps "Export Data Format" list tile
    SS->>SS: _showExportFormatDialog()
    Note right of SS: Dialog with TXT/CSV options appears
    User->>SS: Selects export format (e.g., CSV) in Dialog
    SS->>BSP: exportFormat = (selected format)
    BSP-->>SS: Notifies listeners (UI updates)
    SS->>User: Dialog closes, selection applied

Loading

File-Level Changes

Change	Details	Files
Implemented Settings screen UI and interaction logic	Created SettingsScreen StatefulWidget with main scaffold Added CheckboxListTile for auto-start toggle Added ListTile to display and change export format via SimpleDialog Managed radio selections and updated provider values via GetIt	lib/view/settings_screen.dart
Extended BoardStateProvider to store settings and gate USB listener	Imported constants and added exportFormat and autoStart fields Wrapped USB event stream subscription in autoStart check Retained existing detach logic and notifyListeners on disconnect	lib/providers/board_state_provider.dart
Added new string constants for Settings screen	Defined labels for Settings, Auto Start, export options, and cancel button	lib/constants.dart
Integrated Settings route into main navigation	Imported SettingsScreen in main.dart Registered '/settings' in the routes map	lib/main.dart
Updated navigation drawer to handle Settings navigation	Added logic to push or pop until '/settings' on drawer tap	lib/view/widgets/navigation_drawer.dart

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[Vidhijain20]

@CloudyPadmal @AsCress Could you please review this as well ?

[github-actions]

Build successful. APKs to test: https://github.com/fossasia/pslab-android/actions/runs/15117143419/artifacts/3153025629

[CloudyPadmal]

Fetch the text from the constant file

[Vidhijain20]

@CloudyPadmal Done.

[CloudyPadmal]

Create a colors.dart file in the same directory as the constants.dart and move all the hard-coded colors to colors.dart.

Then use those here and rest of this file.

[Vidhijain20]

Thanks for your suggestions ! I've implemented this.

[AsCress]

LGTM @Vidhijain20 !