The Destination Selection subnode under
Periodic Condition nodes has been removed in version 6.1 and has been replaced by an optional
Destination Selection section in the
Settings windows for
Periodic Condition nodes. It can still be added from the API for backward compatibility. The only difference in behavior for old API code when using Destination Selections is what the entities of the feature’s selection are when it is set to all boundaries:
In new 2D models, when adding Fillet and
Chamfer features, you typically do not need to set the
selectinsketch property, as it is set to
on by default.
where <format> can take the following values:
nativeascii,
nativebin,
parasolidbin,
parasolidascii,
acisbin,
acisascii,
iges,
step,
stlbin,
stlascii, or
dxf.