I'm not even going to attempt to respond to all the back and forth here since I'm a half dozen messages behind. Alexander sounds like he's basically figured out how things work and he's correct that the work is almost complete. The complex case of setting B is only available if setting A is selected is not something that is handled by the current setup. Do you have a use case that needs this? The case of the special C++ warning dialog isn't handled either, but could probably be integrated with the progress monitor or the error reporting if it's really super-critical (doesn't seem to be in my mind).
Responding to a variety of Andreas' points: - If you don't see the SWT specialization of ImportCommon, you don't have the argoeclipse-core project checked out. The class is org.argouml.argoeclipse.internal.core.imports.ImportSources. - ImportCommon is a lot more than 6 weeks old. The original importer settings design was done by Bogdan Pistol as part of the 2006 Google Summer of Code and I did the refactoring of the trunk in late 2006. - "How long will it take?" (Asked several times) Probably a few hours. Do you have a time critical need? Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
