Hello Bruce,
xmetman wrote:
That fix works for Delphi 2007 but not for Delphi XE6 as far as I can see which is most frustrating!
The workaround (setting HighBrush.Style to bsSolid at runtime) seems to work fine for me with v2014.12 and RAD XE6.
Could you please check the paths?
xmetman wrote:I read your reply with interest - I don't particularly like your fourth point about Do-It-Yourself fixes to bugs in TeeChart - I simply don't have the expertise to be able to do this - and that's why I bought TeeChart in the first place - to help me create attractive charts quickly.
I'm sorry, don't take me wrong! We don't consider that 4th point as the preferable way to go either. I just considered it was worth to mention having the sources opens that door. We are always happy to hear suggestions and critics about the code we've written.
xmetman wrote:I have been a visual programmer since 1995 when Delphi first appeared. I have invested in three different versions of TeeChart over the years from you, and when I drop a High Low series on a form I fully expect to be able to flood fill the area between the lines in any color. If that doesn't work then its not much use. Any productivity gains that I may have made are worth little if I have to apply so many work rounds.
I'm sorry for the inconvenience that bug generated. I've set a higher "importance" to
the ticket.
xmetman wrote:I have spent the last six months migrating numerous applications that use TeeChart that I created in Delphi 2007 and get them to recompile in Delphi XE6, there seemed to be little backward compatibility between the latest version and TeeChart 8, everything needed tweaking, and quite a few things like the color fill issue, are still not working. I have never found TeeChart particularly easy to work with and that's why I have requested help on countless occasions in the past and I am very grateful for this. At the moment it appears to me that TeeChart is in a terminal decline I just hope that I am wrong.
The last TeeChart VCL v8 version was published on March 2011. So, a jump from v8 to the actual v2014 means several years (more than 3) of changes in the library.
As you probably know we always try to keep backwards compatibility. However, sometimes the implementation of a new feature forces us to break it intentionally, and sometimes I'm afraid we also commit mistakes breaking existing functionalities. That's why we offer the different
support channels, always trying to efficiently identify & solve any problem or request that may be reported.
At this point, the time until we can fix a bug or implement a new feature depends on variables such as the complexity of the problem, impact and the number of issues with even higher priority that claims our team attention.
If there's any specific issue (or a list of issues), reported or not, you want us to give you an update on their status, please don't hesitate to let us know.