On Wed, Apr 21, 2010 at 6:54 PM, Satyagraha <[email protected]> wrote: > Sometimes - but not always. With the problem class I have, I can drag it onto > a package (in the Package-centric view), which appears droppable, but this > has no effect. See also your own comment in > http://argouml.tigris.org/issues/show_bug.cgi?id=5404 which seems related. > > To reiterate an earlier question of mine: after selecting a class, how are > the names in the Namespaces dropdown list in its property panel determined? > What rules/algorithm is involved? Is there any reason why it shouldn't be > every package in the project? > > I have a full checkout and would like to understand this area.
It sounds like you may be starting to wander towards territory that would be more appropriate to the developers list if you're going to be working on the code. One obvious reason that you wouldn't want every Namespace included as a possible candidate is that the namespace/containment hierarchy is just that, a hierarchy, and can't contain cycles. If a package A contains subpackages B & C, none of A, B, or C should be included as candidates. When you say that "sometimes" it's a problem, without providing a specific example that fails to work, you don't give people very much information to help you with. It would be much better if, as Bob suggested on March 26, you created a bug report with an example that doesn't work the way you expect, including a description of what you expect to happen and what actually happens instead. Tom ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=449&dsMessageId=2592753 To unsubscribe from this discussion, e-mail: [[email protected]].
