Skip to content

Automatic number of created part is to big #29

@ThomasAbballe

Description

@ThomasAbballe

Hi all,

I recently had a small issue with a Nastran to Systus translation. VEGA created a part with part id 9999999 (i may have missed a 9 number here) to host elements which appeared in Systus but not in Nastran (I think it was MPC, but it's irrelevant). The resulting model works perfectly.

However, a few of our part management tools don't work with this part, as they create a part of "Part ID+1" to work. In this case, 9999999+1=NaN. That's, frankly, a very poor design of our software, and we filled a bug ticket to solve it. In the meantime, do you think it would be easy to find another default number for part ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions