https://bugzilla.novell.com/show_bug.cgi?id=208075 sh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|sh@novell.com | ------- Comment #11 from sh@novell.com 2006-10-25 05:23 MST ------- The cost of having multi-selection in YSelectionBox or in YTable widgets would be a more complicated API: You could no longer get "the" selected item, you would get a list of selected items you'd have to walk through one by one. And you'd always get a list, even if nothing is selected (list empty) or if only one item is selected (list contains one item). Changing the API for the generic case is something we obviously can't do - we'd break a lot of existing code. So we'd have to add another (yet another) kludge to work around that - use properties "SelectedItem" and "SelectedItems" (or "SelectedItemList") and add something like `opt(`multiSelection) to the respective widgets. And still it would be considerable work to actually use that in existing modules. This smells a lot like overcomplicating things that were once easy to use, and also like another source for really hard-to-find programming errors on the application side. YCP was never meant for sophisticated power-user GUIs. At places where we need that kind of thing the proven approach is to use dedicated high-level widgets (like the PackageSelector, the PatternSelector, the PartitionSplitter, ...). It looks more and more like installation source handling might be another good candidate for that approach. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.