[Light Switch] Enter latitude and longitude manually in Sunrise to sunset mode

[Jaylyn-Barbee]

Summary of the Pull Request

This PR introduces new UI to allow the users to manually enter their lat/long.

PR Checklist

• Closes: Light Switch: Setting location manually without maps #42429
• Communication: I've discussed this with core contributors already. If the work hasn't been agreed, this work might be rejected
• Localization: All end-user-facing strings can be localized
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

[Jaylyn-Barbee]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[niels9001]

Should the lat/lon textboxes be disabled too?

[niels9001]

Do run this method too when manually entering values?

Should the save button be disabled ubtil we checked if the entered values are actual numbers?

[Copilot]

Pull Request Overview

This PR updates the Light Switch location dialog to improve user experience by allowing manual latitude/longitude entry alongside automatic location detection. The primary button changes from "Select" to "Save" and the UI is reorganized to present input fields and a detect button together.

• Adds manual latitude/longitude number boxes for direct user input
• Replaces auto-trigger geolocation on dialog open with an explicit "Detect location" button
• Restructures location result panel to display sunrise/sunset times more clearly

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
Resources.resw	Updates button labels and resource strings, adds new latitude/longitude headers and detection button text
LightSwitchPage.xaml.cs	Refactors geolocation from auto-trigger to button click handler, adds value change handler for manual coordinate entry
LightSwitchPage.xaml	Restructures location dialog UI with number input boxes, repositions detect button, and adjusts result panel layout

Comments suppressed due to low confidence (3)

src/settings-ui/Settings.UI/SettingsXAML/Views/LightSwitchPage.xaml:1

• Inconsistent indentation: this line uses a tab character while surrounding lines use spaces. The file should maintain consistent indentation throughout.

<?xml version="1.0" encoding="utf-8" ?>

src/settings-ui/Settings.UI/SettingsXAML/Views/LightSwitchPage.xaml:1

• Inconsistent indentation: this line uses a tab character while surrounding lines use spaces. The file should maintain consistent indentation throughout.

<?xml version="1.0" encoding="utf-8" ?>

src/settings-ui/Settings.UI/SettingsXAML/Views/LightSwitchPage.xaml:1

• Inconsistent indentation: this line uses a tab character while surrounding lines use spaces. The file should maintain consistent indentation throughout.

<?xml version="1.0" encoding="utf-8" ?>

[Copilot]

The LatLonBox_ValueChanged handler does not enable the primary button when valid coordinates are entered. The GetGeoLocation_Click handler sets LocationDialog.IsPrimaryButtonEnabled = true on line 138, but this handler does not. Users who manually enter valid coordinates cannot save them because the primary button remains disabled (initialized to False on line 203 of the XAML).

Suggested change

	LocationResultPanel.Visibility = Visibility.Visible;
	LocationResultPanel.Visibility = Visibility.Visible;
	// Enable the primary button when valid coordinates are entered
	if (LocationDialog != null)
	{
	LocationDialog.IsPrimaryButtonEnabled = true;
	}