Trip Planner / Dates not chronological when I print the trip plan

Hi,

the Trip Planner (in Basecamp Mac Version 4.2.2.0) seems to be messed up when I try to print my trip.

Here is what I have: We start on the 7th September and our tour will be till 3rd of October.

Everything is planned and looking fine so far. But when I try to print I get a plan that starts on the 7th and ends on the 8th of September. After the 7th September I have day three the 9th September - then the tour is ok till the 3rd October followed by the 8th September as the last day of the trip (but shows Day 2). At the top it says my trip from 7th to the 8th September.

I changed a few days and now it is even more messed up - now I do have the 3rd October followed by the 19th of September and then by the 8th of September so things are going to be more and more worse the more I change my trip. I would need to do more changes but I can't really plan until I don't have a chronological order. Is there a way I can fix this somehow or do I need to wait to get this fixed in an update (if it is a bug!)?

Please help.

Many thanks
Yogie

0 Former Member over 11 years ago

Can you upload a screenshot of what you are seeing?

0 YOGIE.DE over 11 years ago

Hi,

here are the screenshots, one shows the tour overview, you can see at the left hand side that the dates are chronological...

... the other is the Trip Planner print preview where the things are messed up ...

I had to put the last screenshot together to show you what it is about as you would not see it without editing as you have to scroll down....
You can see the header says that the trip is from 7th September till 19th September. The 3rd October is our last day, but you can see the 3rd October is followed by the 8th September and then the 19th September.

When I now would start to change a date in between that date would then the end date of the trip and would follow the 19th September...

Cheers
Yogie

PS: I'm using a German Version of BaseCamp but when I post something in the German forums there is no reply and the forums are not that active over here.

0 Former Member over 11 years ago

Thanks for the additional info. I am able to recreate this issue on my side now, and we are working on a fix.