waypoints | 用python实现大疆无人机M600航点规划任务 | Robotics library

You've set this up very nicely. Your RoutingMachine component is well written, and you already have your ref to it. Great. Let's examine RoutingMachineRef in the console:

As you can see, if you dig through, the svg path component can be found at RoutingMachineRef.current._line._layers[some_layer_id]._path. But watch out because sometimes leaflet routing machine will draw multiple layers (separate svg layers for rounded line caps, etc). You can actually access these dom elements directly through the RoutingMachineRef.

I'm not sure which one of these gets the .animate css class in your code, but you can probably just add your event listener to each of these. I imagine only one of them is going to actually animate (potentially a problematic assumption there), so the event listener will only fire once, when the one that has the .animate class stops animating:

You cannot convert the Route object that you have received from the REST API call to a Java or Kotlin object that the HERE SDK can understand - as JavaScript/JSON vs. Java / Kotlin are not compatible, and most importantly, the Route object cannot be generated on app side from scratch as no constructor is publicly accessible.

You can only try to create the route again with the same parameters that you have used on your web portal. The results may differ, as it is a new calculation and time and traffic situation may change the route.

A better solution may be to talk to the HERE support team and ask them to allow creating routes from a given RouteHandle. The route handle uniquely identifies a route and it is just a String representation of a route. The REST API can generate the handle and the HERE SDK can then consume it, in theory ...

You can use onChange to monitor the status of RegionIndex. It might look like this (replacing your onAppear):

Good afternoon,

From my experience calling Javascript in a Blazor Component requires use of the IJS runtime. Here is the Microsoft Blazor Documentation for this issue:

https://docs.microsoft.com/en-us/aspnet/core/blazor/call-javascript-from-dotnet?view=aspnetcore-5.0

Essentially you use the IJS runtime to call specific methods from your custom JS documents.

The issue is with this commented line,

You will notice that in the docs, createcontrolcomponent lists only one argument, which is a function to create the instance. You are expecting it to behave like createlayercomponent, which takes two arguments. In createlayercomponent, the second argument is a function to update the layer component when the props change. However, createcontrolcomponent offers no such functionality. react-leaflet is assuming, much like vanilla leaflet, that once your control is added to the map, you won't need to alter it directly.

This gets a bit confusing in terms of leaflet-routing-machine, because you don't need to change the instance of the control, but rather you need to call a method on it which affects the map presentation.

IMO, the best way to go is to use a state variable to keep track of whether or not your waypoints have changed, and use a ref to access the underlying leaflet instance of the routing machine, and call setWayPoints on that:

You're using createLayerComponent, but the routing machine is actually a control. Use createControlComponent.

I also recommend making this as a separate custom component, as described in the docs, rather than putting it in a useEffect. The docs are hard. Feel free to read How to extend TileLayer component in react-leaflet v3? to see if that helps in understanding how to make custom components with react-leaflet v3.

Here's how you'd do it:

To answer your two newly added questions:

1. Even if I set the rotationSpeed to 30 it's still rotating kind of slow. Why 30 is so slow?

Your current timestep is set to rotationSpeed * Time.deltaTime. As you mentioned, rotationSpeed is now 30, but what is Time.deltaTime? Time.deltaTime is the amount of seconds between frames, meaning it is 1 / framesPerSecond. Generally framerate is ~60, so for the example we'll call it 1/60 or 0.016666667. When multiplied by your constant of 30, we get 30/60 or 0.5.

The parameter you are using in RotateTowards is maxRadiansDelta. From the wiki, this parameter is:

The maximum angle in radians allowed for this rotation.

As to why your rotation could be defined as slow, is you are moving at roughly 0.5 radians per second. If you increase this value from 30 to something like 60, you then move to 1.0 radians per second and so on.

1. The rotation is on all the axis like in this screenshot but I want it to rotate only on the Y but because to make the capsule stand I have to set the X to -90 when rotating on the Y it's changing the capsule-like scaling it. I want the capsule to like spin around itself.

The issue here is that RotateTowards will orient your object on all axes to directly take the forward direction and point it at your goal transform. I believe something like this could work?

I saw your previous post before it was deleted, so here is the answer I had for your original question of moving between waypoints by both rotating and movement with the option of what occurs at the end of the motion. I can answer your current question if answering your last deleted question has still not solved your issue.

Instead of using the Update function to handle the rotation and movement between a series of waypoints in a list, I would recommend using a Coroutine. If you are unfamiliar, think of them as a process that handles small increments of work overtime and will jump back where it leaves off. It should simplify the issue of rotation and movement into smaller bite-sized pieces of logic, allowing an easier time to understand your issue.