Beta 4.0.0.5 Changes

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.
  • Former Member
    0 Former Member over 12 years ago
    Thank you. I'm going to hope that this hold true for the waypoint/via move as well. :)


    Can you elaborate on this?
    Do you want the behavior to be exactly the same as previously (Option+dragging for waypoint moving, no Option for shaping)?
    Or would you prefer not having Option used at all, in moving waypoints as well as shaping routes?
  • Can you elaborate on this?
    Or would you prefer not having Option used at all, in moving waypoints as well as shaping routes?

    Yes please. This would be my preference.
  • Good news everyone! The next version of BaseCamp will have a preference that allows you to move waypoints, or drag routes/tracks without holding option. This preference will need to be added manually to the BaseCamp preferences file. If you're interested, here's how you will be able to do it:

    (Note, these steps should only be followed by advanced users!)

    1. Run 'Terminal'
    2. Enter the following command exactly as shown.
    defaults write com.garmin.BaseCamp NoOptKeyToMoveUserDataKey -bool true

    3. Run BaseCamp to verify that the drag behavior has changed.

    Note: to revert BaseCamp to its previous state enter the same command as above, but change the 'true' to 'false'.
  • Cool. Although I think not-so-technical folks would like to have this option as well. Will this "setting" get overwritten when BaseCamp is updated?

    Cheers,
  • Thank you!! And I'll echo Dan's question about the updates overwriting the setting.
  • Thanks for that addition.

    Makes me wonder if there are other hidden settings we can access using that method?
  • In the future we may add this as a setting in the preferences window, but for now it can only be set via the method described above. Updating BaseCamp will not override this setting. Your preferences should always remain the same from version to version.
  • Former Member
    0 Former Member over 12 years ago
    Good news everyone! The next version of BaseCamp will have a preference that allows you to move waypoints, or drag routes/tracks without holding option. This preference will need to be added manually to the BaseCamp preferences file. If you're interested, here's how you will be able to do it:

    (Note, these steps should only be followed by advanced users!)

    1. Run 'Terminal'
    2. Enter the following command exactly as shown.
    defaults write com.garmin.BaseCamp NoOptKeyToMoveUserDataKey -bool true

    3. Run BaseCamp to verify that the drag behavior has changed.

    Note: to revert BaseCamp to its previous state enter the same command as above, but change the 'true' to 'false'.


    This is available in version 4.0.0.8 beta and will be included in the upcoming 4.0.1 release.
  • This is available in version 4.0.0.8 beta and will be included in the upcoming 4.0.1 release.


    Easy enough and it works. Thank you very much.
  • Greetings,

    I've been updating each beta release for the last year and starting in late July I've observed that the size of the BaseCamp_Backup file has grown exponentially. While I have a significant quantity of Waypoints and Tracks in my Collection, I did not add many during this period. In fact the net quantity may be similar.

    Here's the history of file bloat:
    BaseCamp_120724.Backup 28.4 MB
    BaseCamp_120725.Backup 47.3 MB
    BaseCamp_120730.Backup 88.9 MB
    BaseCamp_120802.Backup 121.4 MB
    BaseCamp_120806.Backup 145.2 MB
    BaseCamp_120810.Backup 173.2 MB

    MacBookPro8,3, 8 GB RAM and a 250 GB Solid State SSD.
    System 10.6.8

    Thanks,
    KM


    This problem will be fixed in the upcoming 4.0.1 release. We will make an attempt to circle around and clean up the unnecessary files in a future release as well. Thanks for reporting the issue.