11-10-2011 10:44 AM
In the Array to Cluster primitive why is the default cluster size *9*? What kind of a default value is that?! Who's decision was this? Can anyone ever think of a time where you needed a cluster size of *9*?
11-10-2011 10:50 AM
Well, there has to be a default and "1" is too small and "1M" is too big, so we need something inbetween. What default value would you suggest? 😉
"9" is actually a good default value, because is is somewhat unusual. If the number 9 appears in a post dealing with clusters, we immediately know what the problem is. 😄
11-10-2011 10:52 AM
As Aristos answered here: "why not?"
11-10-2011 01:01 PM
And I always thought the preson who was developing the function was listing to this at the time!
-AK2DM
11-10-2011 02:20 PM
11-10-2011 06:57 PM
@Darin.K wrote:
Assuming there is still a valid and necessesary use for this function I disagree that there needs to be a default value. I would really prefer a Coerce to Type function for this, but I think the existing function should break code until a value is set. Add a red X to the icon as a reminder. Is the final value really 9 so often that it is worth the implied shortcut?
Good idea...make the node drop broken until you set a cluster size. I'd vote for that on the idea exchange.
11-11-2011 12:09 PM
@Darren wrote:
Good idea...make the node drop broken until you set a cluster size. I'd vote for that on the idea exchange.
Idea posted here:
11-11-2011 01:50 PM
11-14-2011 07:31 AM
As an old hardware guy I assumed it was "eight bit plus parity" for nine bits. Some old mahcines did have byte level parity checking.
Ben