>>>>> On Sun, 22 Aug 2004 11:41:56 +0200, Danny Backx <[EMAIL PROTECTED]> said:
Danny> I've tweaked your example a bit and attached the outcome to this
Danny> message.
Danny> With a one line change to List.c, the result of running the test
Danny> program is :
Danny> dell: {40} list2
Danny> Selection (count 1) : 2
Danny> Selection (count 1) : 2
Danny> Is this what we want ? (This is copying Motif's bug ...)
Not quite -- you tweaked away some of the subtly :-)
In the original, the second setting was
items2[0] = XmStringCreateLocalized("c");
items2[1] = XmStringCreateLocalized("a");
items2[2] = XmStringCreateLocalized("b");
XtVaSetValues(list, XmNitems, items2, XmNitemCount, 3, NULL);
and in Motif this changes the selection to 3 (because the item labelled "b"
remains selected). The output from the attached code in Open Motif 2.2.2 is:
Selection (count 1) : 2
Selection (count 1) : 3
as if says under the doc for XmNselectedItems:
"If XmNitems is changed such that the list now contains items matching
previously unmatched items in XmNselectedItems, those new items will also
appear selected."
__Martin
list-selection-loss.c
Description: Binary data
