Frederik Ramm schrieb: > Hi, > >> The only one I still run into is when trey to select an area I need to >> find a point sufficiently far away from any surrouning node or way, >> otherwise I end up moving said node/way. Especially when you're zoomed >> out a lot, finding somewhere to start the selection area fro mcan be >> quite a challenge. >> >> The only solution I can think of are: >> - Seperate select only mode (we've been there) >> > Some people desperately want a select-only mode back and while I > would prefer to have a coherent user interface, it is not impossible > to just reinstate a select-only mode, maybe simply in addition to > what we have. > I'm not sure if this is caused by the need of a seperate mode itself, or simply by the problems people have with the current move operation. Unintentionally moving stuff is more annoying / painful compared to other programs - so this is a critical point for people.
I could imagine that most people can just live with not having a select mode, if the implementation manages that users don't unintentionally move around stuff all the time. It happens for me as well, and that's the only problem I currently have with the new "modeless modes" ;-) >> - Modifier key to disable move (but we've run out) >> Sounds a bit annoying to work with IMO. >> - Change the selection tool so you actually have to click *on* the >> node to move it, and 3 pixels next to it doesn't count. >> Also sounds a bit annoying to work with IMO. > A fourth option that has been suggested is that you would only move > stuff that has been selected in a previous step, i.e. you would not > click on a node, hold the mouse button and immediately move it; > instead you'd have to release the button to complete the select > action, then click again to initiate the move action. > The "pixel treshold" for moving stuff only after a certain "pixel move amount" was exceeded, is the way to go IMHO. BTW, the default number of pixels before a move is performed is very important here, so we might need to experiment with it a bit. If the value is too low, people are still moving things around and if it's too high, it's annoying to use :-) The "two step select" is probably the way to try out next, if people still have big problems with the threshold implementation. Regards, ULFL _______________________________________________ josm-dev mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/josm-dev
