Done and done. Thanks for the fast response. Bug ID# 8171599
On Jul 8, 2010, at 2:11 PM, Troy Koelling wrote: > > On Jul 8, 2010, at 10:48 AM, vade wrote: > >> >> Hello >> >> Question and possible feature request. >> >> Is it possible to have an input port, defined as NSUInteger to have a >> respected minimum value? If a port is defined as not having a menu (no >> QCPortAttributeMenuItemsKey), i cant see why QCPortAttributeMinimumValueKey >> would not be respected. >> >> I cannot get that to work (and I seem to recall it never working). Is there >> a reason that an NSUinteger port type should never have a minimum other than >> 0? I can see many places where having a min defined, sans menu would be >> beneficial, and using a double in the UI would be odd and confusing (ie, >> port numbers, always over 1024, so min would be 1024, etc). >> >> Any thoughts? Am I missing something obvious? > > Yes, as of today QCPortTypeIndex (which would result from NSUInteger) always > starts from zero, and that's probably not correct for the reasons you gave. > Can you please write up a short bug? Thanks! > > Troy >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
