[GExperts-Bugs] [ gexperts-Bugs-3433825 ] Cannot save project after 'Replace components' command

[SourceForge.net <no...@so...>]

Bugs item #3433825, was opened at 2011-11-05 04:17
Message generated for change (Comment added) made by steve_goa
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116240&aid=3433825&group_id=16240

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: Closed
Status: Open
Resolution: Fixed
Priority: 7
Private: No
Submitted By: Steve Faleiro (steve_goa)
Assigned to: Erik Berry (eberry)
Summary: Cannot save project after 'Replace components' command

Initial Comment:
Using: Delphi XE Update 1, GExperts 1.35, CnPack  0.9.9.621, Windows 7 64-bit

In GExperts, after issuing the 'Replace Components' command, trying to save the project results in an AV and the project cannot be saved. 

The only way to proceed after this event is to quit without saving and then restart Delphi.

Note that the components are replaced as expected. However when trying to save the Delphi project it shows the Access Violation error message.

Could this be happening because I have CnPack also installed? 

Is there hope for a fix in the next release or in the source repositiory?

Stacktrace that is displayed along with the AV is attached (please see attached). 

----------------------------------------------------------------------

Comment By: Steve Faleiro (steve_goa)
Date: 2011-11-05 07:52

Message:
Hi eberry, Thank you for responding. If I knew how to fix this, I would
have checked out the source code and fixed this myself. However I don't
have the skills on the GExperts project to fix this. Could you please
indicate whether someone will fix this and push it to the source
respository soon or whether we have to wait indefinitely until the next
release for the fix?

Regards,
Steve Faleiro
ste...@ya...

----------------------------------------------------------------------

Comment By: Erik Berry (eberry)
Date: 2011-11-05 04:34

Message:
Thanks for your bug report.  There is a limitation/bug in Delphi 2010 and
XE where if you assign a Component.Touch property from one component to
another and destroy the original component that the new component becomes
corrupt (it isn't like component/interface references, where they either
auto-correct themselves or are reference counted).

For the moment, you can assign a bi-directional replace component property
map from (for example) TPanel.Touch to TGroupBox.Touch that is marked as
disabled, and that will work around this problem.  Our next release will
not try to assign that property any longer.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=116240&aid=3433825&group_id=16240