On Feb 23, 2012, at 6:16 AM, William Squires wrote: > From what I've read, the NSStepper has a bug (though practically, you'll > never see it); if one were to click the up or down arrow on the control 2^32 > times (assuming it's value is a 4-byte signed int,and is initialized to 0), > it would wrap around (or raise an exception for integer overflow). Probably > not what the user had in mind!
It's pretty irrelevant, because you wouldn't be using a stepper control for values in the billions. That'd be a poor UI. Just like if a table view had a couple billion rows in it in (in 32-bit) it would have broken as well. But it's a terrible thing to do in the first place. ;) > 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. Not really. The control's intended use is to increment and decrement a value. That's what it does. If you're not using the stepper for manipulating a numeric value, you should probably be using a different control. -- Seth Willits _______________________________________________ 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
