Hide "COMPLETE" button from navigation

[stedi-akk]

It would be great to have possibility to hide this button

[Ilan321]

Isn't it already implemented? It's StepperLayout.setCompleteButtonEnabled(bool enabled)

[stedi-akk]

This method disables button click function, and nothing more.

[Ilan321]

Try removing the text and image in the builder

…

On May 3, 2017 10:16 PM, "Dima Stepanchenko" ***@***.***> wrote: This method disables button click function, and nothing more. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#104 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABSLL1kZZdy-p3xysqSa6NUCU44QcgYIks5r2NKlgaJpZM4NPhtV> .

[stedi-akk]

Well, hacks I always can do. But I prefer normal code in my own apps :)

[zawadz88]

Hi @stedi-akk,
Could you provide a use case where this could be useful? Removing the complete button seems like a custom thing and I'm not sure whether it should be a part of this library TBH.
Thanks

[Ilan321]

Having one of those "first run" introduction steppers and then on the last step having the user log in?

…

On May 4, 2017 2:17 PM, "Piotr Zawadzki" ***@***.***> wrote: Hi @stedi-akk <https://github.com/stedi-akk>, Could you provide a use case where this could be useful? Removing the complete button seems like a custom thing and I'm not sure whether it should be a part of this library TBH. Thanks — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#104 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABSLLxgfn2QUwT2gjYbxjlrgcCiTRFLPks5r2bO5gaJpZM4NPhtV> .

[stedi-akk]

I have my own "finish" button on the last "conclusion" step. That button is big, and centered in layout. Generally, my button is more visible to user, than this small "COMPLETE" button.

[zawadz88]

Thanks for your feedback. I'm wondering whether this shouldn't be on per step basis, i.e. showing Next/Complete could be configured on the adapter level with the default being to show the buttons. What are your thoughts?

[Ilan321]

Yeah, implementing this on a per-step basis would be better than just the final step. For example, you could ask the user to log in at the first step and then show the "tour" afterwards.

…

On May 4, 2017 10:11 PM, "Piotr Zawadzki" ***@***.***> wrote: Thanks for your feedback. I'm wondering whether this shouldn't be on per step basis, i.e. showing Next/Complete could be configured on the adapter level with the default being to show the buttons. What are your thoughts? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#104 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABSLL0BF0Ifal5FNl3Q4DHHNBLAdP9_Hks5r2iLhgaJpZM4NPhtV> .

[stedi-akk]

I think StepperLayout.setCompleteButtonVisible(bool visible) would be enough, because this button shows only once (on the last step). "Next" / "Back" buttons are okay, and I think that they should always be visible.

[zawadz88]

I'm leaning more towards what @Ilan321 is saying.
From my perspective, it would be better to handle both buttons as new functionality requests were historically usually raised for both buttons in the Issues.

I'll gladly review any PRs regarding this :)