 | Component editors - all most every component will have one or more
component editors. Right click and double click those
components. |
| Never, NEVER, NEVER, NEVER, NEVER
run your setup program from the IDE UNLESS you have
the parameter TEST on the command line. If you don't
- you'll delete your setup program (just the EXE, not the DPR, DFM,
and PAS files). |
| Do not add TSETUP to your USES clauses. This will
cause your program to link in the component editor support and support for
the property editors - and you don't want that. |
| TSetup 3.00 Beta (and the eventual release version) is completely incompatible
with TSetup 2.20 or prior version. You must uninstall v2.20 and must
re-create any old projects. I know that this is a hassle - but with
the complete gutting of TSetup, I had to do this. Painful, but
worth it. Trying to open a v2.20 project with a v3.x will result in
errors left and right. Since the same files names are being used,
TSetup 3.00 cannot co-exist with TSetup 2.2.0 in the same component library. |
| In C++ Builder v1.0 Professional (even with both patches applied), I had
to REM out line 232 in the file DDEMAN.HPP. It kept generating the
error: Declaration terminated incorrectly. Go
figure.... |
| For most intents and purposes C++Builder v1.0 is like Delphi v1.x.
Not sure about C++ Builder v3.0 since I haven't been able to afford it.
The following features are known not to work in C++ Builder 1.x
1) Shell Links - the editors allow it, but don't trust it. C++ Builder
1.x doesn't have support for the COM objects that are used to access shell
links. |
Aloha Oi Software:
Beta Notes
