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

Value changed triggered only on control change #13

Merged
merged 1 commit into from
Oct 16, 2014
Merged

Value changed triggered only on control change #13

merged 1 commit into from
Oct 16, 2014

Conversation

nicholascross
Copy link
Contributor

Currently this control behaves differently to default iOS controls such as UISlider. When AXRatingView value is set from code it will currently trigger UIControlEventValueChanged; this is not how UISlider works.

UISlider will only trigger value changed event when user interacts with the control to change its value.

UIControl class reference documentation states the following.
"UIControlEventValueChanged: A touch dragging or otherwise manipulating a control, causing it to emit a series of different values."

This commit ensures that UIControlEventValueChanged is only triggered when the value is changed through user interaction.

Also given the potential to break backwards compatibility for some users, if you choose to accept this change it should probably be part of a minor release and not a dot release.

Currently this control behaves differently to default iOS controls such as UISlider.  When AXRatingView value is set from code it will currently trigger UIControlEventValueChanged; this is not how UISlider works.

UISlider will only trigger value changed event when user interacts with the control to change its value.

UIControl class reference documentation states the following.
"UIControlEventValueChanged: A touch dragging or otherwise manipulating a control, causing it to emit a series of different values."

This commit ensures that UIControlEventValueChanged is only triggered when the value is changed through user interaction.

Also given the potential to break backwards compatibility for some users, if you choose to accept this change it should probably be part of a minor release and not a dot release.
akiroom pushed a commit that referenced this pull request Oct 16, 2014
Value changed triggered only on control change
@akiroom akiroom merged commit 631c987 into akiroom:master Oct 16, 2014
@akiroom
Copy link
Owner

akiroom commented Oct 16, 2014

Thank you for your pull request and a kindly words.

Also given the potential to break backwards compatibility for some users, if you choose to accept this change it should probably be part of a minor release and not a dot release.

You are right. I think it is good opportunity to release ver 1.0.0. I will do it.

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.

2 participants