Do I need a brand new workflow for 3.3.1?

Most of my routes were created in older versions of BC, using the method described below. They still work fine in the new BC and in my zumo 660. The problem is, when I try to create new routes using the old method, bad things happen.

Old method: create a temporary list so that the map is clean and uncluttered (the equivalent of a new "instance" of MapSource on a PC). Copy any needed waypoints into the temp list and use them to create a route. Create any new waypoints necessary to force the route and insert them as needed. Copy the route and paste it into an existing list based on how I organize data. So if it's a new route on Cape Cod, it goes into the Cape Cod list. Then I delete everything in Temp so it's ready for the next task.

Why that won't work any more: In BC 3.3.1, if I create a new route in Temp, all waypoints used in that route must remain in the temp folder. If I erase one, it gets removed from the route, no matter where I have copied the route to. If I copy all of the waypoints in Temp and move them with the route, that does not work either, once I erase them from Temp: it still wrecks the route.

Clearly I need to come up with a new workflow, but darned if I can figure out how to 1) start with a clean map, and 2) arrange routes in lists unless I create them in those lists from the get-go.

Thoughts, ideas, comments?

Thanks,

-dan

0 Former Member over 13 years ago

Most of my routes were created in older versions of BC, using the method described below. They still work fine in the new BC and in my zumo 660. The problem is, when I try to create new routes using the old method, bad things happen.

Old method: create a temporary list so that the map is clean and uncluttered (the equivalent of a new "instance" of MapSource on a PC). Copy any needed waypoints into the temp list and use them to create a route. Create any new waypoints necessary to force the route and insert them as needed. Copy the route and paste it into an existing list based on how I organize data. So if it's a new route on Cape Cod, it goes into the Cape Cod list. Then I delete everything in Temp so it's ready for the next task.

Why that won't work any more: In BC 3.3.1, if I create a new route in Temp, all waypoints used in that route must remain in the temp folder. If I erase one, it gets removed from the route, no matter where I have copied the route to. If I copy all of the waypoints in Temp and move them with the route, that does not work either, once I erase them from Temp: it still wrecks the route.

Clearly I need to come up with a new workflow, but darned if I can figure out how to 1) start with a clean map, and 2) arrange routes in lists unless I create them in those lists from the get-go.

Thoughts, ideas, comments?

Thanks,

-dan

Well, yes, you do need a new method. Remember that this is a database and you are "Copying" the Route and Waypoints to a new List. They are just "copies" or pointers to the Original data in your Temp folder. If you want to work the way you did in MapSource you need to DUPLICATE the Route and then copy it to the new folder. Then you can Delete it in the Temp and the Route and it's waypoints will reside "as originals" in the new folder. Just remember to only do a Delete on the Duplicated Route in the Temp folder. You can then do a "Delete from My Collection" on all of the other data or the Temp folder itself if you want to.

Cheers,

0 danham_ over 13 years ago

Dan,

Thanks for the reply.

I do know about BC being a database and Lists containing pointers, but remain puzzled why the old method worked before, in earlier versions of BC and RoadTrip.

But that side, do you have any suggestions for dealing with the duplicate waypoint name problem (start becomes start1) which happens when you duplicate a route?

Thanks again,

-dan

0 PSEABOLT over 13 years ago

I think it a bug that will be fixed. A work around is to copy the route to a list, go back to your work list and delete the route from that list. Once the route is deleted you can delete the waypoints from the work list and not remove them from the route.

I thing the bug is that deleting a waypoint in a list used in a route in the list deletes the waypoint from the route and this should not be happening unless you are in the routing dialog or delete from the collection.

0 danham_ over 13 years ago

Doesn't work. As soon as I delete any of the waypoints from the list in which the route was created, the route is damaged.

EDIT: Found a workaround. I can duplicate the route and copy the original to a new list, then go back to Temp and delete the waypoints and the route survives. I created a Smart List called "Garbage" that consists of waypoints within 1 day old and that lets me clear out the duplicates with "1" after the name without having to search My Collection for them.

-dan

0 PSEABOLT over 13 years ago

It worked for me but I did not delete the work list. If that is the case an empty list would not be that bad until they get it fixed.

0 PSEABOLT over 13 years ago

I just repeated and it worked for me. I created a work list. Added two waypoints to the work list. Created a route. Moved the route to the list where the that contained the waypoints. Deleted the route and check for the route. Deleted the first waypoint and the route was ok. Deleted the second waypoint and the list was ok. Deleted the work list and still had a good route.
This has got to be a bug. I basically use the workflow you describe except I start a new list for the trip and don't move and delete.

0 danham_ over 13 years ago

Probably my fault, but I can't follow what you are saying.

I create a list called Temp and in it I create two waypoints, called start and finish. Then I create a route using those two. I copy the route and paste it into a list called Testing. The if I delete either or both waypoints in Temp, the route is destroyed.

If I duplicate the route in Temp, then copy the original to Testing and delete the duplicate route, I can get away with deleting start and finish in Temp without wrecking the route in Testing. But then I have start1 and finish1 in My Collection.

-dan

0 PSEABOLT over 13 years ago

See Blue insert

Probably my fault, but I can't follow what you are saying.

I create a list called Temp and in it I create two waypoints, called start and finish. Then I create a route using those two. I copy the route and paste it into a list called Testing. The if I delete either or both waypoints in Temp, the route is destroyed.

Yes this is true because there is a bug in the new release. With start and finish and the Route (start to finish) in the same list. If you delete start or finish, BC edits the route as if your are using the routing window you get when you double click the route.

If I duplicate the route in Temp, then copy the original to Testing and delete the duplicate route, I can get away with deleting start and finish in Temp without wrecking the route in Testing. But then I have start1 and finish1 in My Collection.

I just drag the route to testing. Next I delete the route in Temp list. IF the route is not in Temp list, I can delete start or finish from Temp and the route in Testing is fine. The key is deleting the route first such that BC does not edit the route when a waypoint is deleted from the list. The reason your second attempt works, you delete the route from Temp before you delete waypoints. There is no need to duplicate the route in Temp list.

-dan

0 danham_ over 13 years ago

Thank you very much for the explanation. Much appreciated.

I'll save my "Garbage" smart list for those times when I do want to duplicate a route.

-dan

PS: As I "practiced" with this method, it became clear that it is vital that you delete the original route from Temp after moving it and prior to deleting any waypoints in Temp.

0 Former Member over 13 years ago

You guys already figured it out. There is a bug - regression to earlier route-copy issues.

Hopefully when they fix this we will have the ability to have duplicate Names.

Cheers,