Should be better, now. - Chris -
On Sun, Jan 11, 2009 at 2:23 AM, Chris Browet <[email protected]> wrote: > > > >> I have now played a bit with the new unified Select and Move mode. As >> far as I understand it, you can select objects normally, e.g. by >> clicking on them. When you select an object, you can then move it right >> on. Moving the mouse cursor out of the selected object reverts to Select >> mode. Hovering the selected object again shows the Move cursor. >> > > Right you are. > >> >> Now here's a testcase for you: Get a way with some nodes. Select one of >> the nodes. Now alternately hover the node and the way it belongs to. Do >> that slow and a bit quicker. When moving from the node over to the way, >> Move mode remains active. Go back and forth a bit, sometimes Select move >> is active over the not-selected object, mostly Move mode remains active. >> So this behaves quite non-deterministic. > > > I'll look into that. > >> >> >> Is that by intention or should you really only be able to move the >> selected object? I can't really figure out from the code what is >> happening or why. Maybe something in >> EditInteraction::snapMouseMoveEvent() or >> GenericFeatureSnapInteraction::updateSnap(). >> > > It is so by design. That's the only way I can think of to determine the > intentions of the user. Moving an selected object seems the natural outcome > when dragging it. > >> >> Another thing I found out, but it's only a discovery: Double-click on a >> node. On the first click it's selected and on the second click it's >> moved a tiny bit. This happens if you double-click not exactly at the >> node's position but within the snap area. The node will be moved right >> under the mouse cursor then. So this unified mode is not recommended for >> people who always double-click on things, no matter what. > > > Shouldn't be so. I'll look into it > > Regards > - Chris - >
_______________________________________________ Merkaartor mailing list [email protected] http://lists.openstreetmap.org/listinfo/merkaartor
