Subject Re: [IBO] Builder C++ XE install
Author Lester Caine
Support List wrote:
>>> I've been here before and I know I fixed a couple of these problems, but
>>> hit a brick wall with the earlier builds. This is done with the latest
>>> build
>> ...
>> OK I need to check back through ALL of the versions since BCB6 to pick up
>> the change notes ....
> Do you mean the release notes of IBO?

No - Builder6 to BuilderXE has had a lot of changes each version, so for
instance I needed to work through the Builder2009 change notes to find the right
answer to the vcljpg change ;)

>>> Notes on trying to get running on BuilderXE ...
>>> Dropped IB_JPEGImage.pas because vcljpg.bpl is not available, should be
>>> in websnap.bpl but that is not available on pro version of RAD Studio XE
>>> :(
>>> Why vcljpg should be locket to a more expensive version I don't know.
>>> FIXED - vcljpg.bpi -> vclimg.bpi ( NOT as flagged in various update
>>> pages)
> I am not familiar with the _CXE package files. Are these files you are
> creating in order to specifically address things?

All I have done at this stage is taken the _C6 project and allowed Builder XE to
'update' them, giving me an _CXE set ... which I need to copy to you.

>>> platformdefaultstyleactnctrls.obj not found after dropping designd?? -
>>> not available ( Running C++XE only version of RAD Studio so I can't
>>> check theDelphi copy at the moment )
>> Added AcntMan package to .pas file, and vclactnband.bpl to allow to
>> compile
>> Install gives @Ibodataset@TIBOWideStringField@ could not be located in
>> IBO40XRT_CXE.bpl
> What version of IBO sources are you using?
> Just recently I discovered I neglected to properly register that class.
> Perhaps you should get updated to the very latest sources here. ...

>>> IB_Monitor.pas
>>> 'AnsiChar' to 'string' warning on mkLitCriteria I think
> I do not get such warnings in the regular Delphi XE.

I suspect a setting thing there, but it is just the mkLitCriteria which seems to
be miss matched.

>>> IB_Export.pas
>>> Various 'AnsiChar' to/from 'string' warnings
> Yes, the port of this and IB_Import.pas are yet unfinished.

Good to know what not to worry about just yet.

>> Not sure if these are caused by needing to set the default character type
>> in C++ 'mode' - can't see where the problem is at the moment
> As you know, I am unfamiliar with anything specific to C++. Please let me
> know what you discover here.

Since I have the full RAD Studio, I could drop back to Delphi ... but the large
wodge of code I need to update is all Builder6 ...
I'm having to relearn just about everything since RAD Studio is very different
to Builder6!

>>> Will not install 'Jconsts' also exists in package 'vclimg150'
>> Cleared when the vcljpg.bpi -> vclimg.bpi switch was made.
> Good to hear.
>>> will not install
>> @Ib_parse@ExtractFieldsIntoList$qqrx20System@UnicodeStringsp16Classes@TStr
>> ingo
>>> could not be located in IBO40CRT_CXE.bpl
> Hmmm... I did recently make a change to the ExtractFieldsIntoList() routine.
> I wonder if this affecting things.

It's not something I need loaded myself, just looking at for completeness, so I
can come back to it.

>> The next problem is more critical, and I have been here before!
>> IBO40EDT_CXE is
>> compiling OK, but when I try and add an ib_session object to an empty form
>> the
>> color entries are converted back to numbers and no TColorList is presented
>> to
>> chenge them.
>> ib_connection alos fails when trying to select edit with an error in a
>> color value.
> Did you install this package after compiling it?
> Its sole job is to provide property editors.

Since Delphi AND C++ are now just handled in the same IDE I've not wiped
everything and started again yet. DelphiXE just built and loaded, and C++ used
the D2011_CDT library happily, but without the EDT functions. This is a major
complaint about the way Embarcardeo have done things since we can't now simply
switch between Delphi and C++ projects! This may be causing my problem as I did
have D2011_xx running first.

>> I drop EDT, but the color dropdowns are still not present, so that is a
>> function
>> of the normal comonent loading that I'm not understanding?
>> The GOOD news is that I have actually compiled a working program by hand
>> editing
>> the components ... something I did not manayge with the previous builds
>> ... so
>> I'm sure this is just a matter of something not being set right.
> Sounds like you are very close to having things working.
> I hope I can help you work through these issues.

I do need some input from someone who understands the property editor area.
Something is not compatible between the two versions :(

Lester Caine - G8HFL
Contact -
L.S.Caine Electronic Services -
EnquirySolve -
Model Engineers Digital Workshop -
Firebird -