[josm-dev] JOSM Fail

[D Tucny]

2009/1/17 Rolf Bode-Meyer <robome at gmail.com>

> 2009/1/16 Sascha Silbe <sascha-ml-gis-osm-josm-dev at silbe.org>:
> > On Fri, Jan 16, 2009 at 02:21:27PM +0100, Pieren wrote:
> >
> >> Where is the limit of making harder commands for _intentional_ actions
> >> just to prevent _unintentional_ actions ? It is very hard to find the
> >> right balance between newcomers and experimented users.
> >
> > This isn't about newcomers vs. experienced users. I _am_ experienced and
> > during my normal work I _often_ move objects when I want to select
> something
> > instead, just because JOSM binds two separate actions to the same input.
>
> Huh? What two separate actions? The same action (moving) _should_ need
> the same input (click and drag) regardless what is to be moved.
>

I guess it's the select box and drag move being both the same that's
referred to here...


>
> > If there's a config option I have to set to prevent it from happening:
> Fine
> > for me. I need special configs for most programs anyway, this won't make
> a
> > difference.
>
> Having said above in my work with JOSM accidentally dragging a way
> almost only happens when I want to add a new node by clicking a
> virtual node.
> Right now CTRL *prevents* creating a new node when clicking on a
> virtual node. So from this experience I would see reversal of
> CTRL+click on a way as improvement.
>

I preferred the old modeful JOSM, but, short of splitting out the modes
again, perhaps some tweaking of the sensitivity to nearby objects would make
it more difficult to select features you don't want to and easier to select
them you do, as long as you are reasonably accurate with your clicking...

d