In article <mpro.l1iahf04r94g003qb.lists(a)stevefryatt.org.uk>,
Steve Fryatt <lists(a)stevefryatt.org.uk> wrote:
On 26 Apr, Chris Young wrote in message
> > Drags on treeview nodes need to gain an icon to drag, to
> > that a drag is in progress and make it clear to the user that there
> > is something to drop.
> The first of these - obviously the icon displaying bit is
> ideally we need a line drawn on to show where the item is going to be
> dropped, which probably ought to go in the core (the frontend has no
> knowledge of where the gaps between lines are anyway).
> There was another one relating to dragging which has been
> before - drag-selection boxes (bounding boxes, crawling ants or
> whatever you want to call them) need implementing. My opinion is that
> along with the line indicating where an item is being dropped, the
> drag-select box should also be drawn by the core.
Yes, I agree that drawing it in the core would be simplest.
I think this would have to be partly handled by the core, at least,
because as with the drop-line, I don't think we know whether the mouse
drag starts over a node or the space between nodes. We would also have
to know which nodes fell into the resulting drag area, so as to select,
deselect or toggle them.
I think once a treeview drag starts, the core needs to tell the front end
how the drag has been interpreted, like the browser window drag code.
This way the front end can tell if the drag is a selection drag or a node
drag. If the latter, the front end would show the icon to indicate
something's being dragged.
Michael Drake (tlsa) http://www.netsurf-browser.org/