Two bug reports

Former Member
Former Member
1. Since a few weeks Basecamp takes ages to recognize my Oregon 300. All other Garmin programs (Web Updater, MapSource) recognize it without trouble. It does correctly show up as drive in Windows.

Only BaseCamp takes ages. If I leave BaseCamp running, after 20 minutes or so, the device typically shows up. But sometimes it does not show up at all.

BaseCamp does not seem to have a "rescan" feature to manually start looking for devices (as all other Garmin tools have). That would be a useful addition.

I currently resort to MapSource to get my tracks out of my device and then manually import them to BaseCamp. But of course that is a lot of additional work, and also it is not feature complete, as MapSource does not support Geocaches.




2. There is a bug with the "properties" dialogue that opens when you double click a track or a waypoint or a geocache etc.: BaseCamp apparently remembers where this window was last located on the screen.

But imagine the window was located on the bottom right corner of your screen when a big screen was attached to your laptop. Then you go on a trip, so now you rely on your laptops native resolution. Now the window is too far to the bottom right to be on screen, so it is invisible, and it seems there is no way to get it back into the visible area.

You need to add some code that verifies whether the saved location is even inside the screen, and if not, ignores the last saved location of that window, and places the window somewhere on screen.
  • Former Member
    0 Former Member
    2. There is a bug with the "properties" dialogue that opens when you double click a track or a waypoint or a geocache etc.: BaseCamp apparently remembers where this window was last located on the screen.

    But imagine the window was located on the bottom right corner of your screen when a big screen was attached to your laptop. Then you go on a trip, so now you rely on your laptops native resolution. Now the window is too far to the bottom right to be on screen, so it is invisible, and it seems there is no way to get it back into the visible area.

    There are a few ways to move windows that are off the screen. You could try this:
    Double click on a waypoint/track etc to open the properties windows.
    Press Alt+Spacebar, then press M.
    You should then be able to use the cursor keys to move the window back onto the screen.

    Or press Windows Key +Left arrow/right arrow, that should move the window to one side of the screen.
  • Former Member
    0 Former Member
    Thanks. That helps until they fix the bug.
  • Former Member
    0 Former Member
    1. Since a few weeks Basecamp takes ages to recognize my Oregon 300. All other Garmin programs (Web Updater, MapSource) recognize it without trouble. It does correctly show up as drive in Windows.

    Only BaseCamp takes ages. If I leave BaseCamp running, after 20 minutes or so, the device typically shows up. But sometimes it does not show up at all.

    BaseCamp does not seem to have a "rescan" feature to manually start looking for devices (as all other Garmin tools have). That would be a useful addition.

    I currently resort to MapSource to get my tracks out of my device and then manually import them to BaseCamp. But of course that is a lot of additional work, and also it is not feature complete, as MapSource does not support Geocaches.




    2. There is a bug with the "properties" dialogue that opens when you double click a track or a waypoint or a geocache etc.: BaseCamp apparently remembers where this window was last located on the screen.

    But imagine the window was located on the bottom right corner of your screen when a big screen was attached to your laptop. Then you go on a trip, so now you rely on your laptops native resolution. Now the window is too far to the bottom right to be on screen, so it is invisible, and it seems there is no way to get it back into the visible area.

    You need to add some code that verifies whether the saved location is even inside the screen, and if not, ignores the last saved location of that window, and places the window somewhere on screen.


    Noted #2 in our bug database.

    As to #1, BaseCamp should automatically detect new devices on connection. And it certainly should not take 20 minutes. If you copy the Garmin folder from your Oregon to an SD card, disconnect the Oregon and then launch BaseCamp does it go any faster? (Just for trouble-shooting purposes.)
  • Former Member
    0 Former Member
    Noted #2 in our bug database.

    As to #1, BaseCamp should automatically detect new devices on connection. And it certainly should not take 20 minutes. If you copy the Garmin folder from your Oregon to an SD card, disconnect the Oregon and then launch BaseCamp does it go any faster? (Just for trouble-shooting purposes.)


    Just tested it: Also took very long. Not 20 minutes, maybe 5. But maybe that was just coincidence.
  • Former Member
    0 Former Member
    Just tested it: Also took very long. Not 20 minutes, maybe 5. But maybe that was just coincidence.


    So it definitely looks like it's caused by the data that's on the device. Any chance you could make the data (everything you put on the SD card) available to me somewhere? Maybe via Skydrive or Dropbox? And then share the link via PM. Then I could check what's really going on.
  • Former Member
    0 Former Member
    2. There is a bug with the "properties" dialogue that opens when you double click a track or a waypoint or a geocache etc.: BaseCamp apparently remembers where this window was last located on the screen.

    But imagine the window was located on the bottom right corner of your screen when a big screen was attached to your laptop. Then you go on a trip, so now you rely on your laptops native resolution. Now the window is too far to the bottom right to be on screen, so it is invisible, and it seems there is no way to get it back into the visible area.

    You need to add some code that verifies whether the saved location is even inside the screen, and if not, ignores the last saved location of that window, and places the window somewhere on screen.


    Did you actually encounter this problem? Because looking at our code, it looks like we are already handling this.
  • Former Member
    0 Former Member
    Did you actually encounter this problem? Because looking at our code, it looks like we are already handling this.


    Yes just happened over the weekend when I was visiting my family.

    I will send you a PM in a moment with a download like and an encryption PW for the contents of my Oregon 300.
  • Former Member
    0 Former Member
    Thanks for the file. I downloaded it and put it on my SD card and (of course) it shows up for me right away. :(

    So I am not sure why this isn't working on your end.

    I'll look into the dialog positioning.

    Thanks again for all your help, much appreciated.
  • Former Member
    0 Former Member
    Just one more question: I noticed I never actually verified the version you are running. You are running BaseCamp 4.1.2?
  • Former Member
    0 Former Member
    Yes, 4.1.2.

    ----

    I believe I found out what causes the delays: I am using ExpanDrive to map a server as a drive W: in Windows.

    For some reason that I never understood, BaseCamp always thought W: was a Garmin device and listed it as a device in the program. But I never really cared about it.

    With all the testing I noticed that there is the long delay, THEN drive W: appears in BC, THEN ONE SECOND later the Oregon appears.

    So I suspect that BC hangs while scanning W: and cannot recognize other devices.

    I have tested the theory by unmounting W:, and BC recognizes the Oregon almost instantly.

    So the solution would be to either fix BC in such a way that it won't detect ExpanDrive drives anymore as Garmin device; or to add an option to ignore certain drive letters, such as W:.