>> :) This was another bug that is fixed for the next beta. It was a problem with converting some text of "360.0" into 3600 if your locale has certain characteristics. You Europeans with your commas and decimal points all reversed are always causing problems!! :) :) :)


We do our best to keep you busy ! ;-))
Thanks for fixing it !

Hi Michael,

>I kind of try to avoid this type of thing where
>there are similar fields, where one is ignored
>if another is filled...

However in the Array-Curve command prompt there are two fields - Item count and Distance - and an applicable is underlined.
So you can choose either that kind of behaviour or this how you mentioned. Anyway I think it would be useful feature.

>If I understood him correctly, I think that Petr's later
>analysis was a vote for keeping it the way it currently is.

Definitely!

>You Europeans with your commas and decimal points all reversed
>are always causing problems!! :) :) :)

hehe....

Petr

> However in the Array-Curve command prompt there are two fields - Item
> count and Distance - and an applicable is underlined.

I thought you might mention that! :)

The problem is not quite as bad in that case since there are only two fields for the entire command. When there are more fields, this type of implicit toggle becomes more awkward.

It shouldn't be hard to do the toggle switch, I will give that a try.

- Michael

I've got the toggle switch working now for the next beta, so that will let you switch between "Angle to Fill" / "Angle step" methods for the angle field.

There is still quite a bit of other stuff to do before the next beta is ready though.

- Michael

On other quick note on your helix example - another way to extract an edge is to select it and do a control+drag on it which will drag off a copy of it.