🚀 go-pugleaf

"David M. Karr" writes

> Frankly, I wouldn't try to implement it this way.  This would be "surprising"
> behavior from the user's point of view.  I've done this with auxiliary buttons
> attached to the right side of the table that perform "move up" and "move down"
> functions.

That's the way my implementation works this time. I can drag contiguous
selections and single rows. The movement of discontiguous selections is
not useful in my application, because it easy could cause mistakes and
force undo

I don't think, that dragging rows is a "surprising behaviour, but this
is not part of this newsgroup.

> A simple way to provide it from the
> datamodel's point of view would be to implement a "swap" method, given two row
> numbers.  You can then implement any row movement in terms of that method.

That's exactly the way of my implementation. :-)

Regards, Werner