Is it just me and my failing memory or did the route edit workflow change? I could have sworn that yesterday all I had to do was click/hold and then drag to edit, now I need to use the option key as well. I had really hoped the method for repositioning waypoints and via points would have been simplified to just a click/hold drag, rather than complicate the other functions just to be consistent. The reason this is important is that my left hand is usually busy with printed material, guide books, paper amps, notes etc. when I'm route planning. Being able to do all editing and most creation tasks with just the trackpad or mouse would be the ideal situation.
I absolutely agree with KILLTIMER. Adding more key-combo's is not the direction I'd prefer. Keep it simple please. I don't see any reason for the "option" key in any of the current Edit or Move operations.
The change was made to be consistent with out moving waypoints works. The reason for requiring you to hold option is to prevent accidental changes to your data when attempting to pan the map or select multiple items.
The change was made to be consistent with out moving waypoints works. The reason for requiring you to hold option is to prevent accidental changes to your data when attempting to pan the map or select multiple items.
So you've slowed and complicated the process to save us from ourselves? :) Could you please change it back? I bitched when the waypoint movement changed too. Sigh.
The change was made to be consistent with out moving waypoints works. The reason for requiring you to hold option is to prevent accidental changes to your data when attempting to pan the map or select multiple items.
Please don't go down this path. It will ultimately make BaseCamp workflow's so unnatural that nobody will use it.
To use your example, I cannot pan the map when I'm dragging a point and holding the "options" key.
Thanks for the feedback. I'll propose this request and see if we can make these tools not require a special key.
Trying to edit a route while holding down a modifier key is a horrible experience. I have solved it by programming my third mouse button to do Option drag. BUT not that many Mac users use a 3 button programmable mouse.
The typical workflow is that I click and drag the route around to where I want it to go. In order to find the correct place to drop the route it is necessary to Zoom and pan the map. So if the second hand is holding down a modifier key I can't use the arrow keys or + and - to do that moving around.
I know Mac users will not like this statement, but the way it works in MapSource is pretty good, once you pick up the route with the mouse there is no need to hold down anything. so both hands are free to zoom and pan.
So I hope you can get some of the folks who make these decisions of how to implement the interface to understand how this software is used.
[QUOTE=DENNYHENDERSON;141541I know Mac users will not like this statement, but the way it works in MapSource is pretty good, once you pick up the route with the mouse there is no need to hold down anything. so both hands are free to zoom and pan.
I don't think many users of either platform will agree with that statement. I used MapSource for several years and was never able to perfect the right number of clicks it took to get a route point to move.
The change was made so it is consistent with the other movement actions and so we could complete the process of making the hand tool able to work as a selection tool, so you don't have to switch back and forth.
I hope the Point of that is the part that gets understood most.
No matter what method of clicks is used to attach the route to the cursor, The most important thing is that in order to Zoom and Pan while the route is in the rubberband state the operator needs hands free to perform those tasks.
Agreed The method of picking up the route in MapSource is Extremely Awkward.... but, once the route is in the rubberband state the operator has very easy ways to zoom and pan in order to find the precise point (usually an intersection) in order to place the shaping point.
I hope we all agree that the workflow in MapSource is not something that should be implemented in Mac BaseCamp. To Denny's point, the more important issue is natural ease of use with one hand operation for any function that requires repositioning movement on the map. Because, almost every object move/edit on the map will benefit from a concurrent pan/zoom operation.
