With OM, test24 starts with the first item highlighted. Pressing select next
highlights the first 2 items. Press it again and the second and third are
highlighted. Press it again, third and fourth. The stdout follows....
./test24.motif
Before: num selected = 1, text=LessTif, item index=0
...after: num selected: 2
Before: num selected = 2, text=LessTif, item index=0
...after: num selected: 2
Before: num selected = 2, text=Rocks, item index=1
...after: num selected: 2
With Lesstif, test24 starts with no items highlighted. Pressing select next
highlights nothing. Press it again still nothing. Press it again still nothing.
The stdout follows....
./test24
Before: num selected = 1, text=(null)
...after: num selected: 2
Before: num selected = 2, text=(null)
...after: num selected: 2
Before: num selected = 2, text=(null)
...after: num selected: 2
This test is also showing a problem with our paned window. OM displays a giant
sash control.
On 27-Dec-00 at 22:11, Alexander Mai ([EMAIL PROTECTED]) wrote:
>
> Looking for a bug within LessTif's List widget implementation I discovered
> that at least on one Motif version (1.2.4 on DU) it is possible to have
> multiple selected items in a List widget regardless of the selection mode,
> e.g. it might be SINGLE_SELECT. This can be done programmatically
> (as opposed to user interaction e.g. by mouse) using a
> Xt*SetValues(..., XmNselectedItems, ...) call.
>
> Is this for sure a bug, so that LessTif can ignore this strange behaviour
> or is it a "feature" ? Or can anyone tell what OM behaves like?
>
> I added a test for this to test/Xm/List/test24.c.
>
>
> ---
> Alexander Mai
> [EMAIL PROTECTED]
>
>
>
>
