Changes to base classes should propagate to instances or subclasses, unless the instances or subclasses override the base classes somehow. perhaps that is what is happening? If you select "Open instance" instead of "Open actor" you can see what is an override vs. what is inherited from the base class.
An example would help... Edward On 12/4/12 5:12 PM, Ian Szarka wrote:
Hi all. I am after advise about making modular actors. Please respond. I am developing a library of actors, currently I have 20 user actors - many of which do similar things. I have built the actors in a modular way with common functions in a handful of base actors. A few times I have found bugs or need to change base functionality used in all of the user actors. I have put base actors in the “C:\Users\Ian\KeplerData\workflows\MyWorkflows” folder and built the composite user actors using them. However I have found that changes to the base actors do not propagate to the user actors. Currently I am opening each user actor and making the same change for the base actor 20 times! How can I do this so that functionality in base actors is correctly used by other actors. Please help, I am after advise. Regards Ian. _______________________________________________ Kepler-users mailing list Kepler-users@kepler-project.org http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
<<attachment: eal.vcf>>
_______________________________________________ Kepler-users mailing list Kepler-users@kepler-project.org http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
