inconsistency in konqueror

[Raul Fernandes]

> Ah! If the treeview is not updated on *deletion*, that's indeed a bug. The
> treeview should certainly reflect the current status of the filesystem at
> any time.

Not exactly the treeview. The iconview/listview is not updated when the user 
delete a directory. In treeview, the directory is changed, but not in 
iconview/listview.

> As far as the collapsing is concerned, I think you mean a scenario like the
> following: There is a directory A and a directory B (a subdirectory of A)
[...]
> However, I don't know what the casual user expects who KDE is aimed at for
> the most part. Hmm, that's actually an interesting question for the
> usability list, ccing, maybe they have to add something.

I was a windows user, but it was two years ago. This is a windows' behaviour 
(the directory in dirview is always the directory in treeview), but I find 
this is more user friendly. Not all behaviour of windows is user friendly, 
but this one is, IMHO.

> I'm not sure if I understand you, what do you mean with "new selection
> mode"? And how exactly is it different from QT's listview?
>
>From QT docs:

QListView::SelectionMode

This enumerated type is used by QListView to indicate how it reacts to 
selection by the user. 

QListView::Single - When the user selects an item, any already-selected item 
becomes unselected, and the user cannot unselect the selected item. This 
means that the user can never clear the selection, even though the selection 
may be cleared by the application programmer using 
QListView::clearSelection(). 
QListView::Multi - When the user selects an item in the most ordinary way, the 
selection status of that item is toggled and the other items are left alone. 
QListView::Extended - When the user selects an item in the most ordinary way, 
the selection is cleared and the new item selected. However, if the user 
presses the Ctrl key when clicking on an item, the clicked item gets toggled 
and all other items are left untouched. And if the user presses the Shift key 
while clicking on an item, all items between the current item and the clicked 
item get selected or unselected, depending on the state of the clicked item. 
Also, multiple items can be selected by dragging the mouse while the left 
mouse button stays pressed. 
QListView::NoSelection - Items cannot be selected.

>From KDE docs:

enum SelectionModeExt { Single = QListView::Single, Multi = QListView::Multi, 
Extended = QListView::Extended, NoSelection = QListView::NoSelection, 
FileManager } 

The first four correspond directly to QListView::SelectionMode, while the 
FileManager selection mode is defined as follows: 

home: move to the first 
end: move to the last 
PgUp/PgDn: move one page up/down 
up/down: move one item up/down 
insert: toggle selection of current and move to the next 
space: toggle selection of the current 
CTRL+up: move to the previous item and toggle selection of this one 
CTRL+down: toggle selection of the current item and move to the next 
CTRL+end: toggle selection from (including) the current item to (including) 
the last item 
CTRL+home: toggle selection from (including) the current item to the 
(including) the first item 
CTRL+PgDn: toggle selection from (including) the current item to (excluding) 
the item one page down 
CTRL+PgUp: toggle selection from (excluding) the current item to (including) 
the item one page up

I think that the extended mode (from QT) is better. Only my opinion.
Maybe, it is better to change this discussion to usability list.
Sorry for the size of the email.

Regards

Raul Fernandes
rgf at ieg.com.br