Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Re: classes know too much about each other -- yes. This program is about 10 years old and not one that I wrote. It has "interacting" features that create problems -- like tying gui-display+refresh into 1 step that requires calling the data-input routine (i.e. can't refresh w/o pulling in data and adding another column(so columns don't represent a fixed amount of time, but anytime a measurement was made)... lots of little gotchas like that.. trying to restructure to fix, (and learning v4-c++ at the same time; last c++ use was near 15-20 yrs ago w/v1 of C++). will have to study your info more Commented Jun 9, 2014 at 18:46
  • BTW-@Mat, reading your thoughts on class design. If the 'Meter', is like TV network that people watch results on, -- then the network would be a scheduler of programs or 'views', on events. I certainly understand where you are coming from -- as I often get confused about differences between an object also 'being' an 'X' vs. an object having an 'X'. Yet, in standard OO examples, unique traits are often part of an object as the traits characterize the object. Wouldn't that make them appropriate for inclusion as part of the object? Commented Jun 11, 2014 at 1:46