This widget is interesting because I honestly don’t know of an existing iOS app that uses this. Obviously, a +/- device has some utility, but there are also some issues to note from using it.
The concept that is going to take a minute for new users to grasp is that the widget has an internal number; a secret number that can have its bounds adjusted. This number has nothing to do with any real variable you might want the +/- spots to update, so it can be a bit tricky to keep the two straight.
The other thing, and the one thing I think is harder to explain, is that the +/- buttons must be part of the same image. I imagine you could probably make a huge image with lots of transparency to seperate the buttons, but it might be problematic. (I don’t really think there is a smart way to seperate the buttons as part of a single function, so that’s not a request…)
Bugs:
-
Object defaults to display.CenterReferencePoint (#18537)
The behaviour isn’t just inconsistent; since you can set top=y and left=x in the creation table…but these values for some reason only refer to the centerpoint of the image, not the top left corner as you would expect. -
widget behaves strangely if moved after creation. (#18538)
If you attempt to set the reference point and then the x/y values after creation, the - button stops working. Probably some sort of internal alignment error.
Requests:
- A way to read the internal number or at least pass it as part of the event. (Maybe this is already there, but event.value, event.index, event.number and event.id come up empty by default)
- the touch event for the Stepper does not pass event.id or event.target (and thus not event.target.id); one of these would be handy to identify *which* stepper is being pressed
- Similarly, it would be great if the docs explain the event being passed and what values are found within.
- At least on sim, the “acceleration” (when you hold down + or -) seems very slow. It would be great to set a new starting speed; as it is most users probably wouldn’t wait and hold for this duration (maybe it’s faster on device?) [import]uid: 41884 topic_id: 32660 reply_id: 332660[/import]