Hello @Noah-Sager !
Thank you for your reply.
I have tried to reset the widget with no luck.
As far as I understand setTravelMode, its to force the widget to use one of the travel modes already loaded for that routing service. The thing is the travel modes from the actually loaded routing service are not reflected in the widget. There is a method called getSupportedTravelModeNames, which returns the Supported Travel Node names for the routing service used by the widget, and when I call it, I get the names from the previously loaded routing service.
My guess is, even if the widget allows to set a different RouteTask, and it actually starts routing with that service, it doesn't update the rest of the information in the widget itself.
That's why I'm wondering if I'm missing something else I need to do, that maybe is not documented, and it's not just setting the new routeTask, or it's just something that is missing in the implementation of the widget and I'm basically in trouble and have to find another way 🙂
ETA: Migrating to 4x is in the plans but not possible yet. Do you think this is solved in that version?