Could you add OPS_GetCrdTransf3d and OPS_GetCrdTransf2d functions to elementAPI?
Thanks,
Mark
OPS_GetCrdTransfXd in elementAPI
Moderators: silvia, selimgunay, Moderators
no .. you have 2 options:
1) they could go in the elements that actually have them and you could do a dynamic cast to that element type if you have only a pointer to an element, or if you are programming your code in c++ you could just keep pointers to these elements.
2) use the setResponse(), getResponse() methods to do what you want.
the latter is what is normally done for people who want to put code into the platform that does not meet the current interface.
i am not aainst adding things to the interface, the reason i won't add this to the interface is that it is not a generic element thing and i don't screw up the clean interface to suit any particular class. if i did (and i know this from experience) the element and material classes interfaces would grow out of all proportions.
1) they could go in the elements that actually have them and you could do a dynamic cast to that element type if you have only a pointer to an element, or if you are programming your code in c++ you could just keep pointers to these elements.
2) use the setResponse(), getResponse() methods to do what you want.
the latter is what is normally done for people who want to put code into the platform that does not meet the current interface.
i am not aainst adding things to the interface, the reason i won't add this to the interface is that it is not a generic element thing and i don't screw up the clean interface to suit any particular class. if i did (and i know this from experience) the element and material classes interfaces would grow out of all proportions.