Hi,
> In that case, why not have a library package in a separate
> (non-running) model which has the base classes you want
> plus all their specialized classes?
Yes, that is what we thought too.
> Then, in whichever model you export this library package to,
> remove those specialised classes you don't want, leaving
> the base classes and those specialised classes you do.
[...]
> Any good?
Almost ;-) But it gave me some new ideas to experiment with.
I tried following: I put the base classes in a controlled unit,
and when I reengineer some projects that use this classes, at first
I load the
controlled unit in my project and then I start the "update model
from code".
What ist important: You must not reengineer the base classes again,
just
unmark them in the VC-Addin before you start. Rose then takes
the classes from the controlled unit and everything is how I want it
;-))
Said with three words: it works now ;-)
Bye,
Julian
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
