Josef Taylor

> @kaichelliah That makes sense, though if we leave out Poisson, I would suggest leaving all the FE properties as null- the user would need to set these themselves based...

This makes sense to me, and those categories are generally aligned with US code. I like the inclusion of accessory combo types, not to be used in Design. I will...

in SAP2000 and ETABS, combination type (i.e. ULS, SLS) are set per design module, i.e. steel design needs a set of combos for deflection and a set of combos for...

@rwemay @IsakNaslundBh does anyone have strong feelings on this?

Based on the way justification is managed in various softwares, I think there are a few options here: 1. Put the fragment on Bar - GSA will have to create...

@IsakNaslundBh @pawelbaran Doing some issue cleanup, was thinking about closing or changing this issue. From what I understand, we want framingElements to stay center-line justified, so there are two actions...

Seems like a direct translation method from Bar (with justification fragment) to IFramingElement (with RevitProperties assigned) would be necessary, unless IFramingElement also gets a justification fragment

At first I considered we could have a universal class with the properties: - Code - U_mx - U_my - U_mz - U_a - U_vy - U_vz - U_combined However,...

with specific classes, we might have an interface that forces each code-based class to implement: - code - version - combined utilization

Hi @JHenneberg, I'm working in Visual Studio 2022, do you think I'd be able to make similar changes and get it working? @michaelkonecny do you need any help with this...