-
Notifications
You must be signed in to change notification settings - Fork 63
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
Slider presenter #1613
Comments
Another sub-issue: the adapter tolerates string values, including a special care about fractions. See value: aValue
| value |
value := aValue isNumber
ifTrue: [ aValue ]
ifFalse: [
(aValue includes: $/)
ifTrue: [ (NumberParser on: aValue) nextFraction ]
ifFalse: [ aValue asNumber ] ].
^ self presenter value: value asFloat This is candidate to be removed. Just accept numbers is a better option. |
Yes please what a bad idea. May be it should also accept XML, YAML, Java and more! |
@Ducasse What is your opinion about orientation? 2 options:
Both presenter API orientation and automatic orientation are not possible at the same time. |
Another bug: addMark: aString at: aValue
"Add the mark `aString` at `aValue` ."
^ self marks: (self marks
add: (SpSliderMark new
value: aValue;
text: aString;
yourself);
yourself) at least it has no senders, and I tested it with: s := SpSliderPresenter new.
s min: 0.
s max: 100.
s quantum: 1.
s value: 100.
s addMark: 'mid' at: 50.
s open. |
Not included in #1619:
|
hi, @tinchodias |
Thanks @estebanlm good point, I agree. I'm going to delete the color: method from |
So, not yet included in #1619:
I propose, for both cases, to remove the API. The alternatives would be a) to just deprecate instead of removing or b) implement it |
The text was updated successfully, but these errors were encountered: