[josm-dev] 'Modeless' josm bugs/requests

[Ben Robbins]

>> 1* If I insert a node between 2 near ways they merge together. Ctrl
>> clicking can stop this, but the node nolonger insearts if I hold ctrl. 
>> The ctl click is a good
>> idea, but I think it may be better if it merges when you hold ctrl and
>> click but not if you don't.  This way you don't make the mistake, then
>> undo then hold ctrl
>> and redo it.  It would save many clicks.

>I guess it is a simple question of which is more common. There is also
>the idea of somehow throwing this whole "standard behaviour,
>ctrl-modified behaviour, alt-modified behaviour" thing open to user
>preferences, i.e. let the user have a matrix of functionalites and
>input modifier options and select which he wants to trigger which.
>
>This would of course allow endless confusion between people having
>their JOSM configured differently, but on the other hand it could
>allow the "power mappers" better control over their environment, and,
>Java permitting, also the use of a fourth and fifth mouse button, the
>"Windows" key, the "Option" key, and whatnot.
>
>What do people think? More flexibility for the power mapper at the
>possible expense of a configuration nightmare, or rather KISS?

A fully customisable interface would be really nice, but personally I would 
say a few alterations to the current shortcut list would make it suitable 
for almost all. The problem is just when people have differnet keyboard layouts.  
Shortcuts can then be in very inconvienient places.

>>    2* (This may just be in windows) I'm having some difficulty creating
>>    way-segments.  If I select a node and then hit 'n' and drag between, only
>>    sometimes a
>>    new way-segment appears. I'm not shore why,

>You sholdn't have to drag. Just click the destination node, no
>dragging. Does it work?

>Maybe we should add the "helper line" from last selected node to
>current mouse cursor (and make that vanish when Shift is pressed to
>disable auto-connect)?

Sorry, I didn't mean dragging.  The problem is still there when I click.

I think a good solution would be to be able to create way-segments, holding
down the same key that is used to make nodes appear by themselves.  This is currently
shift, but that is a little out the way I think.  I think having 'n' as the hold down
shortcut would be good, as this is the same shortcut to get to the tool.  Although in
saying that, it makes me notice that only 's' and 'n' are really needed now, rather than g/n/m before, so it may
be better to shift it to something like 'a' as then you can cover all the most common
shortcuts quickly. (a/s/c/shift/ctrl).  (note ctrl-shift-p, is the most distant common shortcut currently)

>>    3* The move/select tools being merged has made it quite tricky to select a
>>    very small area as it thinks I'm trying to move a nearby node.  I'm not
>>    shore what
>>    to suggest for this one though.

>It has been suggested to only enter move mode if the node was
>*previously* selected. I am a bit unhappy about this as it would
>require a lot of double-click action (click to select, then drag to
>move). Don't know.

I agree, more clicks is bad.  It's nice to have everything, infront of you, editable in one
click.  Going along the lines of the previous suggestion, and how some other programs do it,
could move become 's'+shift?  This would mean both functions would work in all areas,
rather than sharing space.

>>    4*  If I create/insert a node, I first need to deselect before I can
>>    move.  On creation it appears fixed.  Ideally on creation it could be
>>    moveable as it would be
>>    on selection usually.

>Could be done, probably.

This is really the same problem as above, where more clicks are required than I think is nessesery.

>> 
>>    5* In creating a way without deselecting, no matter how complex or messy
>>    the shape is, it will make it all one way.  Incorrectly orderered ways and
>>    ways
>>    with way-segments facing in different directions can be created this way. 

>Something has to be done there but I'm not sure what exactly. Maybe
>offering a modifier key for creating a new way is sufficient for
>starters.

I think in creating a way, if the same node appaers twice in the order, it should split at the node.
The new (4th way-segment) to connect to that node would then be a contiuation of the original way, with
the loop detatch as its own way.  Then if in starting drawing any new way-segment the node you click isn't
the same as the last node in the order, then it should also break. This would enshore that way-segments don't face
the wrong way in the way.

As a set of rules it sounds simple, but I have no idea if josm 'knows' enough to do that?

Thanks,
Ben


_________________________________________________________________
Feel like a local wherever you go.
http://www.backofmyhand.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/josm-dev/attachments/20071013/9d1c5bf2/attachment.html>