Michael Baytalsky wrote:

> Sorry, it just hurts to see how bad things are and on top of that
> hearing this nice things like "we've added TrayIcon component"...
> what a great achievement! in 2006...

Well you don't want to kill of the market for 3rd party components.


The major thing the VCL needs is unicode. I personally think this one
enhancement would get a number of companies upgrading to the latest
version. Just think if all of those cool DevExpress/TMS (insert 3rd
party here) components supported unicode.


The problem is that Borland has been too conservative about approaching
the unicode subject. They seem to be looking for the perfect solution
which isn't always possible without a little pain.


Having something (that works for 50% of users), is sometimes better
than having nothing.


Also you need to remember that VCL.NET also gets these improvements and
with VCL.NET being the framework of choice for the Compact Framework
this is important. While many don't care about VCL.NET - some folks do.


Some also might ask why the vcl still doesn't have native support for
PNG images, why come controls still don't paint with a themed look and
feel under XP.


Most people that bag the VCL don't seem able (or willing) to respond to
questions such as - what would you like added to the VCL? What
enhancements do you look forward to in upcoming releases? What QC
entries have you made to try and influence the direction of the VCL.


Maybe your QC entries are under a different name because searching on
your surname reveals a donut of entries.


Also don't give me the throw away line that QC doesn't work - because I
assure you it does. Just because report XXX and report YYY aren't
opened doesn't mean that it doesn't work. All you have to look at is
reports AAA to WWW that have been opened/closed (as fixed).


-- 
Compact Framework for Delphi 2006: http://www.jed-software.com/cf.htm
QualityCentral Windows Client: http://www.jed-software.com/qc.htm


Visual Forms IDE Add In: http://www.jed-software.com/vf.htm