Skip to content

Conversation

@segfault-
Copy link
Contributor

figured i would attempt to contribute. let me know if there are any issues

@AlexandrePViana
Copy link

Maybe it´s just me, I read there was a SetActiveIndex property, and even tho I have 0 idea what the 2 booleans in it mean, I can´t get the MudStepper to go to the step I want it to using code. Plus a Disable feature for the Step would be great, I'm currently using the linear function to try to achieve the same goal, but the disable would be 1000x better so that I could allow users to cycle through the allowed steps before they unlock the next ones, if that makes sense.

@mckaragoz
Copy link
Contributor

Maybe it´s just me, I read there was a SetActiveIndex property, and even tho I have 0 idea what the 2 booleans in it mean, I can´t get the MudStepper to go to the step I want it to using code. Plus a Disable feature for the Step would be great, I'm currently using the linear function to try to achieve the same goal, but the disable would be 1000x better so that I could allow users to cycle through the allowed steps before they unlock the next ones, if that makes sense.

MudStepper has SetActiveStepByIndex, it's relatively new method to set an active step programmatically

@mckaragoz
Copy link
Contributor

It is not looking properly for me, could you check it again?

And it also breaking change for the current design. Example the header doesn't support outlined or text variant.

And doesn't the template increase the complexity? Why don't we change the design directly?

segfault- and others added 4 commits April 24, 2023 08:34
# Conflicts:
#	CodeBeam.MudBlazor.Extensions/Components/Stepper/MudStep.razor.cs
#	CodeBeam.MudBlazor.Extensions/Components/Stepper/MudStepper.razor
@segfault-
Copy link
Contributor Author

refactored and added vertical support, check again?

@segfault-
Copy link
Contributor Author

as noted in discord, i updated the pr to address the localization issue

@mckaragoz
Copy link
Contributor

@segfault- and do we have breaking change with this PR, we should notice the users.

@mckaragoz mckaragoz merged commit 6fa1170 into CodeBeamOrg:dev Apr 26, 2023
@mckaragoz
Copy link
Contributor

Thanks 🥇

@AlexandrePViana
Copy link

Was it just my Stepper that completely changed the visuals? I think either make it possible for fullscreen stepper (no padding on the sides) or have an option to have the previous version available.

@mckaragoz
Copy link
Contributor

Was it just my Stepper that completely changed the visuals? I think either make it possible for fullscreen stepper (no padding on the sides) or have an option to have the previous version available.

Do you have a snippet?

@AlexandrePViana
Copy link

AlexandrePViana commented Jul 11, 2023

image
image

Both Images containing the current and previous version. I didn´t make any change to my code. But I leave here the MudStepper Snippet

<MudStepper @ref="_stepper" Color="Color.Primary" Variant="Variant.Filled" HeaderTextView="HeaderTextView.All" LocalizedStrings="GetLocalizedStrings()" Loading="_loading" PreventStepChangeAsync="new Func<StepChangeDirection, Task<bool>>(CheckChange)" Linear="true" DisableStepResultIndicator="true" DisableNextButton="@(item.idIndex == 2 || item.fechado || forceDisable)" DisablePreviousButton="true" > <MudStep Title="Criado" Status="@stepStat(0)"> </MudStep> </MudStepper>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants