Hi Federico,
I wrote this class some time ago and I see nothing wrong in using it for different types than int or double. My only reason for keeping parts in a .cpp file was to have it compiled only once and not in every using code.
A simple solution with the current code would be to use the DECLARE/DEFINE macros in a new file pair like mitkStringVectorProperty.h/.cpp or just adding the string type to mitkVectorProperty.h/.cpp. Given the small class size, I would not mind moving it to header-only, neither. Maybe someone from dkfz can give their opinion.
Best regards,
Daniel
Federico Milano <[email protected]> hat am 19. Oktober 2017 um 18:08 geschrieben:Hi. I was trying to use mitk::VectorProperty with a std::string, since I thought it would be possible (there are some tempting macros like MITK_DECLARE_VECTOR_PROPERTY and MITK_DEFINE_VECTOR_PROPERTY), but the implementation is wirtten completely in a cpp file. I have reimplemented it and moved it to a header file, but I thought that maybe there was a reason for not allowing to easily instantiate the VectorProperty using other types than int and double.------------------------------------------------------------------------------Thanks!Federico
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
