-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Removal of NON-signed LinkPoint access in FixedComp #72
Comments
What am I supposed to do instead of removed |
and instead of |
Ok in principle that should be easy -- but if you have a difficult example please post it!
are both accessed via:
e.g.
Note the +1 that needs to be added to the signed rule. Next we have getBridgeComplement: Actually we also had
Note: that for performance issues we are keeping getLinkString(const size_t) const and Anyone (a) unclear (b) has an edge case that this doesn't work well, (c) thinks I have made a design error -- Please add a comment -- many thanks |
The link points can be accessed from a FixedComp in many ways and this leads to inconsistencies.
The points can be accessed via
Axis via
and strings via
ALL of the NON-Signed calls (taking size_t) are either going to be private OR deleted as soon as possible. Obviously if you are using the signed version you use the convention that sideIndex value of zero is the FixedComp origin, and 1 is the first link point, 2 the second etc , and -1 is the complement of the first link point (axis reversed). etc.
If you were using the old system, size_t sideIndex value of 0, was the first link point, 1, the second etc... This is now depreciated. Obviously as I do this process there is the possibility that errors creep in, please check your models and report or push a patch for any errors please.
I have carried out the first stage of this process removing
If there are any issues please
The text was updated successfully, but these errors were encountered: