BaseCamp 4.3.0.3 BETA is Now Available

I'm not sure why it showed the update message?

Is there a way to import just tracks from my device?

I use a z660, in case that makes a difference.

Currently, everything imports from my unit at once, and it causes a ton of unneeded duplicate routes.

You should be able to just select the tracks and drag/drop them into a list in Basecamp. Is that not working?

New Problem with BaseCamp 4.3.0.3....
I'm running 4.3.0.3 beta on my Home Computer and also on my Laptop computer that goes on the road with me... I use the Backup and Restore functions to move routes back and forth between the two computers, .e.g. performing a back up on the home computer, transferring the back up file to the laptop computer and there, open Basecamp and do a restore function.

This all has worked fine for some time except for the following situation, I've seen only happen with 4.3.0.3.. I used the "Edit, Options, Activity Profile, Add Activity Profile to create a new profile I named "Blue Highways"... and adjusted the speed parameters to reflect back route driving. The thing I did that has started causing a problem in 4.3.0.3 was "Edit Activity Profile" and then I selected a new display image.jpg so the routes using the "Blue Highway" profile would have a different Icon in the Trip Data Folder..

This has worked fine until recently.. When ever I do the backup on one machine move the file over to the Laptop, those routes using the Blue Highway activity profile show up as blank and when that blank area is clicked on, BaseCamp abends.... You should have received a couple of BaseCamp abend reports from this......

Incidentally the .jpg display file I chose for the blue highway profile is stored in the same subdirectory name/location on both computers..

To verify the problem is caused by using a "foreign" user selected display jpg file. I changed my "blue highway" routes back to the standard Basecamp "Car Driving" activity profile, did a backup, transfer to the laptop, restore and the routes all display correctly and no BaseCamp abends.


Here is a link to the icon jpg file I am using for the Blue Highways profile: http://home.4x4wire.com/deddleman/parkway.jpg

------------------------------------------------------------------
04/21 Update: I thought the problem might be related to the jpg file size, so I shrunk the above 250x250pixel jpg down to 50x50 pixel. Problem still occurs.

So I tried this scenario........
After performing the same "File, Backup", transferring the file to the laptop computer, and using "File, Restore" to load the file into BackCamp, I then went into the Edit, Options, chose the "Blue Highway" profile I created, then Edit Activity Profile and saw the display image area was again "blank" (non displayable), I then clicked on "Browse" and RESELECTED my custom 50x50 jpg file, and OK'd.. Problem fixed.. no more Basecamp crashes...

The last scenario above would suggest the problem appears to be that when the display image is changed for an activity by the user, this information about the change (perhaps the program link to the user chosen icon jpg file) is not being preserved in the backup file created by the "File, Backup" menu options.. and when the library data is reloaded into BaseCamp using the (File, Restore menu option), the missing link to the route icon jpg file to be displayed causes Basecamp to abend.

Which also raises an interesting question, since the function is there to change the display image, when a user selects an "external" image, (the jpg I'm using is stored in the same subdirectory as the Basecamp library files), should not the complete jpg file be "absorbed" or stored inside the library backup file? What are the ground rules for using external images? size limitations, etc. Perhaps Basecamp could do a similar function as some forums do for member avatars.. they either warn you the the jpg file is too large and tell you what the limits are, or they automatically shrink the pixel count down to acceptable size..

Is there a way to import just tracks from my device?

I use a z660, in case that makes a difference.

Currently, everything imports from my unit at once, and it causes a ton of unneeded duplicate routes.

You should be able to just select the tracks and drag/drop them into a list in Basecamp. Is that not working?

You're right. I was trying to use the import tool, instead of selecting it in the pane. There are things I'm still trying to get used to with Basecamp, because I didn't use/like it very much before 4.3.0 beta versions.

Thanks for the reminder.

New Problem with BaseCamp 4.3.0.3....
I'm running 4.3.0.3 beta on my Home Computer and also on my Laptop computer that goes on the road with me... I use the Backup and Restore functions to move routes back and forth between the two computers, .e.g. performing a back up on the home computer, transferring the back up file to the laptop computer and there, open Basecamp and do a restore function.

This all has worked fine for some time except for the following situation, I've seen only happen with 4.3.0.3.. I used the "Edit, Options, Activity Profile, Add Activity Profile to create a new profile I named "Blue Highways"... and adjusted the speed parameters to reflect back route driving. The thing I did that has started causing a problem in 4.3.0.3 was "Edit Activity Profile" and then I selected a new display image.jpg so the routes using the "Blue Highway" profile would have a different Icon in the Trip Data Folder..

This has worked fine until recently.. When ever I do the backup on one machine move the file over to the Laptop, those routes using the Blue Highway activity profile show up as blank and when that blank area is clicked on, BaseCamp abends.... You should have received a couple of BaseCamp abend reports from this......

Incidentally the .jpg display file I chose for the blue highway profile is stored in the same subdirectory name/location on both computers..

To verify the problem is caused by using a "foreign" user selected display jpg file. I changed my "blue highway" routes back to the standard Basecamp "Car Driving" activity profile, did a backup, transfer to the laptop, restore and the routes all display correctly and no BaseCamp abends.


Here is a link to the icon jpg file I am using for the Blue Highways profile: http://home.4x4wire.com/deddleman/parkway.jpg

------------------------------------------------------------------
04/21 Update: I thought the problem might be related to the jpg file size, so I shrunk the above 250x250pixel jpg down to 50x50 pixel. Problem still occurs.

So I tried this scenario........
After performing the same "File, Backup", transferring the file to the laptop computer, and using "File, Restore" to load the file into BackCamp, I then went into the Edit, Options, chose the "Blue Highway" profile I created, then Edit Activity Profile and saw the display image area was again "blank" (non displayable), I then clicked on "Browse" and RESELECTED my custom 50x50 jpg file, and OK'd.. Problem fixed.. no more Basecamp crashes...

The last scenario above would suggest the problem appears to be that when the display image is changed for an activity by the user, this information about the change (perhaps the program link to the user chosen icon jpg file) is not being preserved in the backup file created by the "File, Backup" menu options.. and when the library data is reloaded into BaseCamp using the (File, Restore menu option), the missing link to the route icon jpg file to be displayed causes Basecamp to abend.

Which also raises an interesting question, since the function is there to change the display image, when a user selects an "external" image, (the jpg I'm using is stored in the same subdirectory as the Basecamp library files), should not the complete jpg file be "absorbed" or stored inside the library backup file? What are the ground rules for using external images? size limitations, etc. Perhaps Basecamp could do a similar function as some forums do for member avatars.. they either warn you the the jpg file is too large and tell you what the limits are, or they automatically shrink the pixel count down to acceptable size..

I will have to investigate this issue. The thing I will ask first is... are your backups and restores going to/from the same version of BC? If not that might be part of the issue here. If they are than I will have to investigate further.

yes both machines have BaseCamp 4.3.0.3 beta installed and both are running Windows SEVEN 64 BIT OS.

As an additional protection against inadvertently executing 2 different levels of Basecamp code (since 4.2.5 is still loaded on both machines) when new beta code comes out for testing, I remove the current production (i.e. 4.2.5) windows shortcuts from the desktop and start list, leaving only the Basecamp beta shortcuts installed. I can certainly imagine that inadvertently starting 4.2.5 after the beta has been updating the database might create havoc.

thanks for investigating....

You're right. I was trying to use the import tool, instead of selecting it in the pane. There are things I'm still trying to get used to with Basecamp, because I didn't use/like it very much before 4.3.0 beta versions.

Thanks for the reminder.

No problem, glad it's now working for you.

I'm not sure why it showed the update message?

Just checking to see if there's any guidance on this? It wasn't a one-time thing.

yes both machines have BaseCamp 4.3.0.3 beta installed and both are running Windows SEVEN 64 BIT OS.

As an additional protection against inadvertently executing 2 different levels of Basecamp code (since 4.2.5 is still loaded on both machines) when new beta code comes out for testing, I remove the current production (i.e. 4.2.5) windows shortcuts from the desktop and start list, leaving only the Basecamp beta shortcuts installed. I can certainly imagine that inadvertently starting 4.2.5 after the beta has been updating the database might create havoc.

thanks for investigating....

I have corrected for your crash. So hopefully that won't happen anymore.

I was able to reproduce your issue by having the same profile on both machines but with different images. We carry over the images just fine in the backup/restore process. The problem is with the registry. We are not preserving this data so custom profile information is lost in transition. This is a bug of course. For now your crash won't happen but profile data would need to be reapplied. We are aware that that is not ideal, so we do have a new case based on your issue for a future release since this is not a trivial change. This needs to be designed properly so that we do not bounce on people's profile settings by accident.