Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Locking the SeekArc when 360 is reached, instead of starting from 0 #54

Closed
voghDev opened this issue Oct 25, 2016 · 6 comments
Closed

Comments

@voghDev
Copy link

voghDev commented Oct 25, 2016

Hi Neil,

thanks for the awesome work on this fantastic widget. I'm trying to adapt it to avoid more than one "full-turn". that means, when you reach 360 degrees, I want the SeekArc to get stuck in there, instead of starting again from zero. I Had no success yet.

Would you suggest any way to approach this requirement? any ideas or pseudo-code that comes in your mind?
If I find an elegant solution, i'll define a new attribute like lockFullTurn or similar, and send you a PR

Thanks in advance :)

@voghDev
Copy link
Author

voghDev commented Oct 25, 2016

Nevermind. I finally don't need it because I've changed my requirements to bypass this issue. Issue closed 👍

@voghDev voghDev closed this as completed Oct 25, 2016
@tuancoltech
Copy link

Hey voghDev,
I got a similar issue here.
Do you have any suggestion to achieve that?

Thanks,

@gdaniels
Copy link

There's a solution for this on #33. Ideally someone who has more time and energy should fork and republish this library, updating to more recent APIs and responding to the issues and PRs that have accumulated over time.

@tuancoltech
Copy link

Thanks gdaniels,
I'll give it a try.

@tuancoltech
Copy link

Hi gdaniels,

I tried both setting jumpAllowed either from xml or java code but it doesn't seem to take any effect.
The seekbar still keeps going once it reaches the end.

Just copied all the changes you in your PR.
Do you think there's any problem here?

@gdaniels
Copy link

Hey @tuancoltech - I'm not sure what you were trying but I just updated the PR to be buildable with Android Studio 2.3.3 and altered the sample app in the PR to include the jumpAllowed="false" attribute on the basic sample. Works as expected for me - let me know if you see something different?

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

No branches or pull requests

3 participants