William Squires wrote: > Why didn't they just make the NSStepper a custom view that draws two arrows, > and has two sent actions that you can connect? Or even a variation of > NSMatrix with two button cells that look like arrows. That would avoid the > problem entirely, and be more intuitive to use.
Um. Because that's not what the control *is*. An NSStepper is a numeric input, for which the interface happens to be a pair of arrows. It's not just a pair of arrows that do whatever you want in response to pressing on each of them. Think of "stepper" in the context of "motor." If it was just two arrows with connectable actions it would be less intuitive and more difficult to use for what it was designed to do. If you want to augment the intended behavior, KVO is probably the way to go. If you want to do something completely different, your should have your own control and it shouldn't look especially like a stepper. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
