You need to generate the archival code for the class in the originating system and include that with the file-in. The Composition Editor saves stuff in the ENVY repository that the archival code allows you to regenerate. It is better to simply
export the class and preserve all that data when you
import it into the target system.
On Friday, December 6, 2019 at 6:58:28 AM UTC-8, Klaus Breker wrote:
Hallo,
I imported an application via file in into my new VAST 9.2 library. The view is a subclass of #AbtAppBldrView and it runs fine if executed.
When I try to open this view class in the composition editor, I see only an empty window without all the labels, group boxes etc. The mehods #abtBuildInternals and all VisualAge methods on the class side are there.
What went wrong?
Kind regards
Klaus
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
To view this discussion on the web visit
https://groups.google.com/d/msgid/va-smalltalk/ec877d8c-8ab6-4748-bb42-69b828e155b9%40googlegroups.com.
Locked
