MudSwitch doesn't allow a default value when using ValueChanged about mudblazor HOT 5 CLOSED

I see the issue now. I was obviously thrown off by trying to use @bind-Value that I normally would use. Which of course it won't let me use. I never again attempted to "bind" my value to the switch as I assumed it would give me the same error. Value="@groupValue" works as intended and allows me to start it with a true value.

from mudblazor.

Simply set the Value property to true via a variable - https://try.mudblazor.com/snippet/mamIETbBJdVjwnGH

from mudblazor.

Seems like the simple solution, but on my machine if I set Value="true" I cannot uncheck the switch. It stays true all the time and doesn't matter what I do. Everything else in the page works. In the Try MudBlazor thing it works as expected. Here is my exact code.

<MudSwitch @ref="groupBySwitch" Value="true" ValueChanged="@((bool val) => GroupByChanged(val))" Label="@(!groupValue ? "Grouped by Agency" : "Grouped by Entity")" LabelPosition="LabelPosition.Start" />

	// Toggle Group By
	private async Task GroupByChanged(bool isChecked)
	{
		if (isChecked)
		{
			groupValue = true;
		}
		else
		{
			groupValue = false;
		}
		dataGrid.GroupItems();
	}

from mudblazor.

Great. Feel free to close this issue if you're satisfied.

from mudblazor.

Another alternative in .NET 7+:

<MudSwitch T="bool" @bind-Value:get="_isSelected" @bind-Value:set="SetAsync" />
private bool _isSelected = true;
private Task SetAsync(bool newValue)
{
    _isSelected = newValue;
    return Task.CompletedTask;
}

Unfortunately, this syntax is not supported by TryMudBlazor, so I can't show a playground.

But yeah, you never want to do this:

valueSwitcher.Value = true;

This is really bad in Blazor. Forget about the imperative way (component.Parameter1 = v1); only use the declarative syntax (<Component Parameter1="@v1" />).

from mudblazor.