Bug fixes in version 8
Posted: Mon Jun 25, 2007 8:17 am
Hi,
Obviously, version 8 fixes some bugs in version 7 (e.g. memory leak in TBrushDialog.LStyleDrawItem) but not all (e.g. not the wrong resizing of the border editor when running under 120 dpi).
Is there an official list of bugs (not) fixed in version 8?
For me a well-working charting package with as few bugs as possible is more important than new (sometimes esoteric) features. For my customers (i.e. your end users), new features are often confusing.
It seems to me that TeeChart is taking the same road as Delphi: limited bug fixes in existing versions forces developers to purchase new versions, which in addition to added costs may intoduce new bugs and problems for the end users. I think this is something for you guys to think about. Of course, I'm not suggesting that bug fixes for old versions should be free for ever, but maybe there could be an overlap between versions so that one can choose to pay for a bug-fixed version N or for an upgrade ro version N+1. Assuming you use a versioning system, this shouldn't be impossible.
Best regards
Obviously, version 8 fixes some bugs in version 7 (e.g. memory leak in TBrushDialog.LStyleDrawItem) but not all (e.g. not the wrong resizing of the border editor when running under 120 dpi).
Is there an official list of bugs (not) fixed in version 8?
For me a well-working charting package with as few bugs as possible is more important than new (sometimes esoteric) features. For my customers (i.e. your end users), new features are often confusing.
It seems to me that TeeChart is taking the same road as Delphi: limited bug fixes in existing versions forces developers to purchase new versions, which in addition to added costs may intoduce new bugs and problems for the end users. I think this is something for you guys to think about. Of course, I'm not suggesting that bug fixes for old versions should be free for ever, but maybe there could be an overlap between versions so that one can choose to pay for a bug-fixed version N or for an upgrade ro version N+1. Assuming you use a versioning system, this shouldn't be impossible.
Best regards