Related

BaseCamp 3.3.0.2 Beta is available

Former Member
Former Member
BaseCamp 3.3 is here! We are starting off with an early Beta release to give everyone a chance to check out the new features and pound on it for a little bit before we release the final version.

Download it here: http://developer.garmin.com/apps/BC/BaseCamp_3.3.0.2_Beta.exe.

We have incorporated a lot of user requests from this very forum. If your desired feature/bug fix didn't make it into this release, don't hesitate to remind us.

We are very interested in your feedback, please report bugs and oddities you find, and comment on the new features.

This is the change-list from 3.2.2 to 3.3.0.2. I will add some explanations and screen-shots in later posts.

  • Added collapsible list folders and sub-lists for improved organization.
  • Added shaping point support for zumo devices like done in MapSource.
  • Added explicit support for shaping points. These will be transferred to supporting devices.
  • Added support for transfer of waypoint categories on supporting devices. These are displayed in BaseCamp as lists.
  • Added more activity profiles, with improved activity routing on supported maps.
  • Added specific avoidances for various road classes, removed the road selection slider.
  • Added custom activity profiles.
  • Added keyboard short-cuts for editing tools (divide, insert, erase).
  • Added a tools menu for easier discovery of tool keyboard shortcuts.
  • Changed to make GPX files on a memory card directly editable.
  • Changed to read all GPX files on a memory card, similar to how devices behave.
  • Improved graphing of track data.
  • Improved graphing when multiple routes or tracks are selected.
  • Improved layout of geotagged photo, waypoint, route, and track properties.
  • Added additional statistics to route and track properties.
  • Added 'Center on map' check-box on route and track dialogs.
  • Added an easier way to add waypoints to routes (Insert Waypoint button).
  • Added additional data fields to waypoints (such as address and phone number).
  • Added display and updating of date last modified for waypoints.
  • Added display of lists that contain this data item to properties.
  • Added receiving geocache visits from devices.
  • Added logging geocache visits on OpenCaching.com.
  • Added printing of geocaches.
  • Added alternate notification mechanism (less annoying pop-ups).
  • Added display settings to adjust width of routes and tracks.
  • Added support for importing waypoints and tracks from KML/KMZ files.
  • Added suggested file name when exporting (so it isn't always 'untitled').
  • Added more map details for higher detail setting.
  • Added data filters to map view.
  • Added preserving the dialog size for each data type.
  • Added option to reset track's altitude to map data.
  • Added functionality to remember display feature settings per profile.
  • Changed 'Remove List and Contents' to 'Remove list and unique contents'.
  • Added Shift-Delete short-cut for 'Remove list and unique contents'.
  • Improved printing of routes and tracks.
  • Fixed issues with sending routes to the zumo.
  • Fixed elevation profile labels for Windows XP (no longer invisible).
  • Fixed issue when duplicating a route. BaseCamp will now also duplicate the waypoints in that route.
  • Fixed issue with the data filter not being remembered between application runs.
  • Former Member
    0 Former Member
    I agree with TrakBak. To be consistent with Windows (e.g. Explorer and similar applications), clicking on the relevant symbol to expand the item in the left pane never changes what is currently being displayed in the right pane.

    It normally requires that you actually click on the folder to display the folder's contents in the right-hand pane.

    ...ken...
  • 0
    Default
    «*Right-click on a track, Advanced > Set Selected Track to Map Elevation.*»


    Can you try this function again?
    I used it while I had a DEM map loaded in the latest version of this beta, and it did not work for me...
  • 0
    Small suggestion to the program

    Latest units (the newest) allow you to use names for IMG maps other that gmapsupp.img, etc. In fact, you can rename the file once gmapsupp.img is created.

    I am wondering why you don't allow to have your desired name at the time of creating the IMG file. To do so, either you give th option to indicate the model of your GPS in Options (most desired and convenient) or you take into account the GPS model recognized by the program
  • Former Member
    0 Former Member
    Latest units (the newest) allow you to use names for IMG maps other that gmapsupp.img, etc. In fact, you can rename the file once gmapsupp.img is created.

    I am wondering why you don't allow to have your desired name at the time of creating the IMG file. To do so, either you give th option to indicate the model of your GPS in Options (most desired and convenient) or you take into account the GPS model recognized by the program



    I think this is an outstanding idea (defining or recognizing the device model). It would provide opportunity to enable/disable functions that do not translate, and to "map" differences such as "ICON/Symbols A-F are supported on Device BLAH, while A-Z are supported on Device Yada".
  • Former Member
    0 Former Member
    Two Unresolved "Issues" (from Basecamp 3.3.0.2 beta)

    Unwanted / Unexpected Data Deletion:
    https://forums.garmin.com/showpost.php?p=117501&postcount=134

    Folder / List Behavior:
    https://forums.garmin.com/showpost.php?p=118596&postcount=163
    https://forums.garmin.com/showpost.php?p=118554&postcount=162 ~ (original post, see issue #2 highlighted in red)
    note: Issue #1 in post #162 is also still present, but is minor by comparison.
  • Former Member
    0 Former Member
    Unwanted / Unexpected Data Deletion:
    https://forums.garmin.com/showpost.php?p=117501&postcount=134

    Folder / List Behavior:
    https://forums.garmin.com/showpost.php?p=118596&postcount=163
    https://forums.garmin.com/showpost.php?p=118554&postcount=162 ~ (original post, see issue #2 highlighted in red)
    note: Issue #1 in post #162 is also still present, but is minor by comparison.


    I'll try to get the prompt for Shift-Delete into 3.3.1, the folder expand/collapse behavior won't get changed for now (but I did take note, hopefully we can do something about this at a later time).
  • Former Member
    0 Former Member
    I'll try to get the prompt for Shift-Delete into 3.3.1, ....

    Falagar, did you catch my note that Shift-Delete does produce the delete confirmation dialogue if you are deleting individual waypoints, tracks and routes directly from the My Collection list but that it does not confirm deletion when you are Shift-Deleting a folder or list from My Collection?

    I did some further testing and determined the following.

    1. As long as you are trying to Shift-Delete actual objects that exist in the collection -- e.g. waypoints, tracks, route -- you get the confirmation prompt. This works no matter how many levels of nested folders deep the object name is that you are trying to Shift-Delete.

    2. The problem of no delete confirmation exists with both lists and folders. If you Shift-Delete a list or folder, no matter what level of nesting, it's gone immediately. The folder or list are deleted and the objects they pointed to are deleted from the collection. All without delete confirmation.

    So it looks like you are recognizing the need for confirmation when an actual object in the collection is the target but as soon as you get one level of abstraction away (folder, list) you miss the need for confirmation.

    ...ken...
  • Former Member
    0 Former Member
    Yes, I did notice that as well. I'll try to make sure you get a confirmation dialog whenever you get rid of some data for good (disregarding Undo for a second).

    It will just have to be a different text as the old text (Items will be deleted from ALL lists) doesn't apply when you delete a folder/list. Now we will only delete data that is unique to that folder/list.
  • 0
    Route not redrawn when point deleted from list

    When I delete a route point from the route window, the route is not recalculated.
    When I delete the same point on the map, it is.