BaseCamp 3.2.0.10 Beta posted

The crash on startup is solved :)

But i lost some of my tracks, how many i don't know. I have about 2000 or more in my database, so it's hard to discover... But at least 2 :(

Great improvements! Especially the ability to add and move track points with the selector tool.

Thanks a lot,

Oliver

v3.2.0.10

Great work folks! I was a little concerned about the Backup/Recover and Export issues in 3.2.0.9 but you fixed the issues I was having and I was able to recover the original Backup. I've tested 8 different Exports with NO issues.

I really like the Hand/Select tool feature. Makes for fast work on the map.

The Track Point Move with the Selector works very well.

Significant improvement in app performance over all.

One nit-pick, there seems to be reserved space for attached My Garmin Devices when no devices are attached. See below...



Cheers,

Crashes faster and harder now

Sorry, but this is a small step backwards for me. iMac 3.2 gHz running 10.6.7. Used to at least launch before freezing. Now it won't even launch.

Process: Garmin BaseCamp [3502]
Path: /Applications/Garmin BaseCamp.app/Contents/MacOS/Garmin BaseCamp
Identifier: com.garmin.BaseCamp
Version: ??? (3.2.0.10 Beta Rev 24491)
Code Type: X86 (Native)
Parent Process: launchd [1108]

Date/Time: 2011-05-27 13:31:43.385 -0400
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6

Interval Since Last Report: 319165 sec
Crashes Since Last Report: 4
Per-App Interval Since Last Report: 11 sec
Per-App Crashes Since Last Report: 2
Anonymous UUID: E788A5A4-49E4-46AA-8502-543E97F9E31E

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Application Specific Information:
*** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<AppController 0x1f60360> valueForUndefinedKey:]: this class is not key value coding-compliant for the key showHideMiniMapTitle.'


(log truncated as forum won't allow characters to post it all)

-dan

UPDATE: I may have discovered a workaround.

I deleted all my user data and tried launching 3.2.0.10 again. Came right up. I quit the app and went back into the database and copied the old material (not a restore) into the newly formed 3.2 database folder.

When I relaunched the program all is well, so far.

-dan

Other changes in 3.2.0.10 that I'd like to hear your feedback on:

• Lines no longer draw through terrain; drawing style has changed accordingly due to both technical and stylistic reasons.
  
• The divider between devices and My Collection is now draggable and follows subtly different resizing rules.
  
• Zooming with the scroll wheel now works more like 2D's zoom, i.e. it zooms toward the location of the cursor. It's only an approximation of said behavior for technical reasons, so I'd be glad to hear whether or not that behavior makes sense to you.
  
• List name uniqueness is now case-sensitive, i.e. you can have both "My List" and "my list" in your database now. A weird detail, but please tell us if there are any issues with that.
  

Other bug fixes that affect performance/UI:

• Fixed labels being sized strangely in 3D mode when the user zoomed in/out.
  
• 3D performance while idling should be much better.
  
• Cleaned up drag/drop and copy/paste behavior so you can't drag data inbetween lists any more.
  

Other changes in 3.2.0.10 that I'd like to hear your feedback on:

• Lines no longer draw through terrain; drawing style has changed accordingly due to both technical and stylistic reasons.
  
• The divider between devices and My Collection is now draggable and follows subtly different resizing rules.
  
• Zooming with the scroll wheel now works more like 2D's zoom, i.e. it zooms toward the location of the cursor. It's only an approximation of said behavior for technical reasons, so I'd be glad to hear whether or not that behavior makes sense to you.
  
• List name uniqueness is now case-sensitive, i.e. you can have both "My List" and "my list" in your database now. A weird detail, but please tell us if there are any issues with that.
  

Other bug fixes that affect performance/UI:

• Fixed labels being sized strangely in 3D mode when the user zoomed in/out.
  
• 3D performance while idling should be much better.
  
• Cleaned up drag/drop and copy/paste behavior so you can't drag data inbetween lists any more.
  

Much better Terrain draw performance and thanks for fixing the lines. It would still be nice if you could reduce the line width of highlighted Tracks/Routes. Maybe remove the black/gray borders(?) for every color except white would be enough.

Dragging of the divider between My Garmin Devices and On My Computer seems natural but I would still like to have the My Garmin Devices space closed unless there is a device mounted - as it was before.

I have always preferred the "zoom-around-center-of-cursor". This is much more intuitive and requires considerably less dragging of the map after a zoom. With this feature and the added "select" feature now associated with the "Hand Tool" I can really get around the map and my data much faster and I'm not constantly changing tools as I had to previously.

I'm not a big fan of "case sensitive" naming in an application. Leads to confusion for this old guy:confused: and I often have duplicates when I don't want them. I'm not sure what the use-case would be for having case-sensitive naming?

I would still like to have "full-screen" mode under "View" options. I use shortcut keys a lot when working on the map (less now with the new features for Hand Tool) and having more map is alway a better experience.

Cheers,

I'm now experiencing the bug in which BC displays in 700-mile scale when it launches, regardless of where I left it when I last used it. This happens every time I launch.

UPDATE: now it's behaving randomly at launch; sometimes @ 700 miles, sometimes where I left it.

-dan

It would still be nice if you could reduce the line width of highlighted Tracks/Routes. Maybe remove the black/gray borders(?) for every color except white would be enough.

The lines are significantly thinner now for tracks than they were in 3.2.0.9, both selected and unselected; the point rendering and arrow could be enough to differentiate selected data, but we're worried about removing outlines from selected data because of possible difficulties in finding the one selected line in a pile of unselected data.

Dragging of the divider between My Garmin Devices and On My Computer seems natural but I would still like to have the My Garmin Devices space closed unless there is a device mounted - as it was before.

That's a known issue; I should've noted it. The minimum size for the device list is now larger than it should be.

I'm not a big fan of "case sensitive" naming in an application. Leads to confusion for this old guy:confused: and I often have duplicates when I don't want them. I'm not sure what the use-case would be for having case-sensitive naming?

Users were getting confused by our case insensitivity when they tried to recase a list/folder name and got told "this list already exists"; this is a side effect of fixing the technical reasons causing case rather than an explicitly requested feature.

Thanks for the feedback :).

PAXTER1,

I understand the difficulty in choosing the highlighted line width. It is better and I neglected to mention that. Thanks.

I guess the Case sensitivity could be good to have sometime but not so good others. I certainly can live with this and it just keeps me on my toes. :)

One new anomaly in app behavior - if I set the app's Dock Options to "Keep in Dock", when I terminate the app's Icon is no longer in the dock. When I restart the app and look at the Dock Options, it shows "Keep in Dock" as checked.

Have a great weekend - even though I get a good deal of it, I miss the Arizona sun :(

Cheers,