#97 expected behavior when there are 2 anns that can fill a slot

[Philip Ogren]

If there are 2 annotations that can fill in a slot and one of them is already filling in the slot, then clicking on the addValue button will automatically swap the values. You can duplicate this with the following:

1) create a class A1 that has a slot hasA2
2) create a class A2
3) set the value type constraint on hasA2 to be of type Instance with the allowed class being A2
4) leave the multiple cardinality box for hasA2 unchecked
5) create two annotations of type A2
6) create one annotation of type A1.
7) fill in hasA2 for the A1 annotation with one of the two A2 annotations
8) observe what happens when you click the 'Add Instance' button for the A1 annotation's hasA2 slot.
9) click the button a few more times to watch the values of the slot get swapped repeatedly.

This feature/bug was introduced by accident when I got around to removing the values already given for a slot from the list of candidates for a recent version (somewhere 1.5 or later)

So, is this a feature or a bug? I'm not sure. I think I like this behavior - but it might be confusing.

[Philip Ogren]

Logged In: YES
user_id=1052182
Originator: YES

changed priority because I'm not sure that this is even a bug.