.NET MAUI中无可见Picker时，如何编程唤起选择弹窗？

以下是几种实用的实现方案，可根据需求选择：

方案1：使用隐藏的原生Picker控件 #

这是最简便的方案，直接复用原生Picker的弹窗逻辑，仅将控件设为不可见：

步骤1：在XAML中添加隐藏Picker #

<!-- 放在布局任意位置，设置为不可见 -->
<Picker 
    x:Name="HiddenPicker" 
    IsVisible="False"
    ItemsSource="{Binding SelectionOptions}"
    SelectedItem="{Binding SelectedOption}"
    />

步骤2：代码中触发弹窗 #

在需要唤起弹窗的地方调用Focus()方法即可：

// 唤起选择弹窗
HiddenPicker.Focus();

注意：部分平台（如iOS）可能需要额外确保控件已加载完成，可在OnAppearing后或通过Dispatcher调用。

方案2：自定义Popup模拟Picker样式 #

如果需要完全自定义弹窗的UI和交互，可使用.NET MAUI内置的Popup（或CommunityToolkit.Maui的Popup组件）：

实现自定义弹窗 #

public class CustomPickerPopup : Popup
{
    public event EventHandler<string>? OptionSelected;

    public CustomPickerPopup(List<string> options)
    {
        // 用CollectionView展示选项
        var optionList = new CollectionView
        {
            ItemsSource = options,
            ItemTemplate = new DataTemplate(() =>
            {
                var label = new Label { Padding = new Thickness(16, 12) };
                label.SetBinding(Label.TextProperty, ".");
                return label;
            }),
            SelectionMode = SelectionMode.Single
        };

        optionList.SelectionChanged += (s, e) =>
        {
            if (e.CurrentSelection.FirstOrDefault() is string selected)
            {
                OptionSelected?.Invoke(this, selected);
                Close();
            }
        };

        Content = new VerticalStackLayout
        {
            Children = {
                new Label { Text = "选择选项", Padding = new Thickness(16, 8), FontAttributes = FontAttributes.Bold },
                optionList
            },
            WidthRequest = 300
        };
    }
}

调用自定义弹窗 #

var options = new List<string> { "选项A", "选项B", "选项C" };
var popup = new CustomPickerPopup(options);
popup.OptionSelected += (s, selectedOption) =>
{
    // 处理选中结果
};
await this.ShowPopupAsync(popup);

方案3：直接调用平台原生API #

若要完全脱离MAUI的Picker控件，可针对不同平台编写原生代码，获得最纯粹的原生体验：

Android平台实现 #

#if ANDROID
var currentActivity = Platform.CurrentActivity;
var alertBuilder = new AndroidX.AppCompat.App.AlertDialog.Builder(currentActivity);
alertBuilder.SetTitle("选择选项");

var optionsArray = new string[] { "选项1", "选项2", "选项3" };
alertBuilder.SetItems(optionsArray, (sender, args) =>
{
    var selected = optionsArray[args.Which];
    // 处理选中逻辑
});

alertBuilder.Show();
#endif

iOS平台实现 #

#if IOS
var pickerView = new UIKit.UIPickerView();
pickerView.Model = new PickerViewModel(new List<string> { "选项1", "选项2", "选项3" });

var alertController = UIKit.UIAlertController.Create("选择选项", null, UIKit.UIAlertControllerStyle.ActionSheet);
alertController.View.AddSubview(pickerView);

// 设置PickerView布局
pickerView.TranslatesAutoresizingMaskIntoConstraints = false;
NSLayoutConstraint.ActivateConstraints(new[]
{
    pickerView.TopAnchor.ConstraintEqualTo(alertController.View.TopAnchor, 16),
    pickerView.LeadingAnchor.ConstraintEqualTo(alertController.View.LeadingAnchor, 16),
    pickerView.TrailingAnchor.ConstraintEqualTo(alertController.View.TrailingAnchor, -16),
    pickerView.HeightAnchor.ConstraintEqualTo(200)
});

// 添加确定/取消按钮
alertController.AddAction(UIKit.UIAlertAction.Create("确定", UIKit.UIAlertActionStyle.Default, _ =>
{
    var selectedIndex = pickerView.SelectedRowInComponent(0);
    var selectedOption = ((PickerViewModel)pickerView.Model).Options[selectedIndex];
    // 处理选中逻辑
}));
alertController.AddAction(UIKit.UIAlertAction.Create("取消", UIKit.UIAlertActionStyle.Cancel, null));

Platform.CurrentViewController.PresentViewController(alertController, true, null);

// PickerViewModel实现
public class PickerViewModel : UIKit.UIPickerViewModel
{
    public List<string> Options { get; }

    public PickerViewModel(List<string> options) => Options = options;

    public override nint GetComponentCount(UIKit.UIPickerView pickerView) => 1;
    public override nint GetRowsInComponent(UIKit.UIPickerView pickerView, nint component) => Options.Count;
    public override string GetTitle(UIKit.UIPickerView pickerView, nint row, nint component) => Options[(int)row];
}
#endif

方案选择建议 #

• 优先选方案1：代码量最少，完全复用原生Picker的交互和样式，适配成本低。
• 若需自定义UI，选方案2：灵活性高，可完全控制弹窗外观。
• 若需极致原生体验或特殊需求，选方案3：需要维护多平台代码，但体验最贴近原生系统。

内容的提问来源于stack exchange，提问作者Dryzler