KListBox/KIconView/KListView

[David Faure]

On Sunday 01 January 2006 16:24, Till Adam wrote:
> Today I looked into porting KListBox, since I need it for KLineEdit, where 
> it's used for the completion box, which I need for KInputDialog, which was 
> the thing I initially wanted to port. As far as I can see the raison d'etre 
> for KListBox, KIconView and to an extend also KListView is treefold: 
> 
> 1) support for honoring the system settings for single/double click selection 
> of items 
> 
> 2) support for timer based auto-selection on hover
> 3) mouse cursor change over items. 

Hi Till,
Today I looked at KListBox and found pretty much the same as you did a year ago ;-)

1) is not addressed yet. I heard rumours of a "proxy style" which would forward all
calls to another style, allowing to change the behavior of one method from any existing
style? If we had that, we could use such a proxy qstyle for itemviews, to make it return
the right value for QStyle::SH_ItemView_ActivateItemOnSingleClick, independently from
the actual style implementation.


Benjamin: if you don't think there should be a KListView and KListWidget, then
2) and 3) need to be in QListView. Do you think this would be possible?

You wrote:
> I am not sure what you are referring to with number 2  looking at the 
> klistbox. klistview and kiconview docs I don't see any mention of a timer or hover.
This is auto-selection, as can be configured in KControl in kde3 (and as Windows does in
single-click mode).
You leave the mouse over an item, and after a few seconds it gets selected automatically. 
This goes very well with single click mode. As does mouse cursor change over items, to 
indicate that single-click will activate.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).