BaseCamp v4.2.4 update...

Former Member
Former Member
Well, I just updated my BaseCamp to v4.2.4. Surprised I don't see any mention of it here.
  • Former Member
    0 Former Member over 11 years ago
    I appreciate that you continue to post an App Store version of BaseCamp and I hope that you won't stop posting the non-App Store version.
  • Former Member
    0 Former Member over 11 years ago
    I just upgraded to 4.2.4 from 4.1.2 and have noticed that when I "Get Info" on a track, I no longer can see the track point time down to the resolution of seconds. I changed the system level time formats to include seconds for the "short" time format and that seemed to fix the problem. The down side, is that now I have seconds displayed in a lot more places where that resolution is over-kill and a waste of space.

    While it may be handy to follow a generic system-wide standard, displaying the time of a track point is much different than displaying the creation time of a file. This is one instance (of probably many) where using a generic configuration parameter does not work well. The track point time should always be displayed with the seconds. If this seems to be an issue with other users, it should probably be a BaseCamp preference instead of using the generic system one.
  • That would be a bug. It should not be using the short time for track time. We probably aren't going to create our own time format configuration, but it used to use the Medium Time setting and for some reason that was changed. We'll fix that for 4.3. Sorry for the inconvenience.
  • Former Member
    0 Former Member over 11 years ago
    I can wait for 4.3. The local configuration idea was if it was a purposeful change, so having it tied to the medium time format works. Thanks for the feedback.
  • We'll look into the case sensitive issue for 4.3, but ironically App Store sandboxing makes it difficult to stay fixed.


    I don't understand how sandboxing has anything to do with case sensitivity of filenames, but if you say so, fine.

    4.3.1 doesn't mention case sensitive and doesn't fully communicate with my 1490 when my MacOS 10.9.3 is booted from a case sensitive filesystem.