While working on Issue 5 and Issue 6 I realized that the code is a mess. If
you look at the code you will notice that 3 classes declare and maintain
separate sets of the configurable variables (such as x, y, background
color, text color, opacity and etc...).
The Config.cs file handles reading and writing these values to and from a
file. PerfMonG.cs grabs those values, and stores them as class fields.
Finally PropertiesDialog.cs also stores local values of these variables. I
have no clue why I did it this way, but it's messy and it needs to get
refactored.
Ideally, these variables should be contained in a single class (Config?),
and the other classes should simply use Properties to access or modify them.
The code will need to be refactored before I feel comfortable incrementing
the minor release number to 0.3.
Original issue reported on code.google.com by maci...@gmail.com on 23 Jun 2007 at 7:57
Original issue reported on code.google.com by
maci...@gmail.comon 23 Jun 2007 at 7:57