[BUG?] Vector creates "NaN" in linear repeater

kkNielsen
kkNielsen Denmark
Hi, I think i have found a bug in the smartcomponent system. I have a linear repeater called "stackspawn", which i use to make a stack of my parts. However, I have found that when setting all the values in the vector to zero (see image). The offset of the linear repeater becomes NaN.

Is this a feature or a bug?

Comments

  • Maxim Riabichev
    Maxim Riabichev Sweden admin
    edited September 9
    Hi kkNielsen,

    Why would it be meaningful with an offset of [0,0,0]mm?

    Do you have any use cases where this feature would be useful?

    Thanks!

    Maxim Riabichev
    PC Software Support Engineer
  • Hi kkNielsen,

    Why would it be meaningful with an offset of [0,0,0]mm?

    Do you have any use cases where this feature would be useful?

    Thanks!
    Would you consider 0 to be a number or "Not A Number" ? 
  • Hello Tompan,

    Please consider that the SmartComponent in question is a LinearRepeater. The reason 0 isn't an acceptable number, in this case, is because that would make the LinearRepeater into a Source SC.

    That's why I asked if there perhaps was some case where a 0 on a LinearRepeater would be useful.


    Maxim Riabichev
    PC Software Support Engineer
  • kkNielsen
    kkNielsen Denmark
    @Maxim Riabichev Thanks for answering.
    I would not consider 0 to be NaN. It took quite a few hours of debugging to figure out that the LinearRepeater was the cause of my problems.
    In my case there were use cases where I only had 1 object in my stack and then I would not specify the offset, If  I have more than 1 object in my stack i would add an offset based on the amount of objects.