On 26 Apr, Chris Young wrote in message
<[email protected]>:
> On Mon, 26 Apr 2010 22:47:01 +0100, Steve Fryatt wrote:
>
> > http://wiki.netsurf-browser.org/Todo/RISC_OS_frontend
>
> A couple of those need implementing in the Amiga frontend code too IIRC:
>
> --8<--
> Drags on treeview nodes need to gain an icon to drag, to indicate that a
> drag is in progress and make it clear to the user that there is something
> to drop.
>
> Drags on treeview nodes need to utilise AutoScroll when available.
> --8<--
>
> The first of these - obviously the icon displaying bit is frontend, but
> 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).
That makes sense, I think.
> The second I hadn't actually thought about.
This is part of the RISC OS drag API, so I had assumed it would fall to the
front-end to handle. There's no reason why the core couldn't do it, I
suppose -- it could work through the scroll_visible callback.
> There was another one relating to dragging which has been mentioned 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. Have you added such a thing to the RISC OS frontend
> code?
Not yet: the whole user-facing part of the treeview drags leave a lot to be
desired in the new RO frontend at present.
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.
--
Steve Fryatt - Leeds, England
http://www.stevefryatt.org.uk/
