Maël Hörz wrote:
Quote
report it as test case error (which it isn't).
A test case error means that the user is not using the product as it
is designed to be used. There is a documented way to add version
information to a BDS project - use the project manager. If you do that
it works properly. So this _is_ a test case error.
The report is based on doing something completely different - using a
resource script created by a different tool and adding it to the
project. I have seen no documentation that that is supposed to work,
and have provided information on how to correct the script so that it
can be used.
If you don't want to change the script, then adding the res file
created by the third-party software also works.
Quote
There are quite a lot of (year) old bug reports that never were fixed,
Which is exactly why, as a user of BDS, I have volunteered to serve as
a sysop and try to help clear up the backlog. Good progress has been
made in the time I have been helping with this. By sending a report
like this to the internal system at CodeGear I would only be impeding
that process.
With the release of BDS 2006 Borland had already decided to drop
support for MFC and they do not provide support for importing other VC
oriented files. This was a conscious decision based on the limited
value for such efforts. Maybe when the actual bugs in the product are
fixed, they can reconsider that decision.
Quote
This special thing might not be of importance for many,
but just because it doesn't crash your app doesn't mean
it shouldn't be fixed. Such attitude gives a
If something were broken, I would agree that it should be fixed. In my
opinion only the referenced qc report is broken. If one of the other
hundred or so other sysops disagrees with me, the report will be
opened, but I see no one but you arguing for that to happen.
I have already wasted more time than is reasonable on this, and the
issue is closed as far as I am concerned.
- Leo