Closed tferr closed 7 years ago
Why not adding setters and getters instead of making these fields public?
I think setters would only be useful if there were public methods to parse .traces files in a modular way. Right now there aren't: all the .traces parsing is done in a monolithic block. Getters would make sense, thought. Do you want me to replace it with getters()?
(Now I see this merge-without-waiting-long-enough-for-feedback was a bit despotic. I just thought nobody would care :) )
Adding getters and setters would simply be more in line with the ImageJ coding style.
Having private fields and get/set methods allows to change the implementation later on, without having to change the API in a backwards-incompatible way.
But don't worry, I just stumbled upon this and was tempted to ask, while having not much insight into the details of the source code...
This fixes a bug reported by Volko Straub (see tferr/hIPNAT#5 and tferr/hIPNAT@c45704a)