You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is unclear to me how, or if, we can set correct execution speed on the command part of the VDP. It seems like it does things immediately by default? I'm reliant on the copy command being executed over time, and not instanltly, so I'd like to know how this can be achieved.
The text was updated successfully, but these errors were encountered:
As of the current version, unfortunately, this is not possible.
The VDP commands use a simplified implementation, and all operations happen
instantly, and only the completion flag tries to estimate and report the
correct command duration.
As for the STOP command, it should only affect the report of termination
and the completion flag, but the operation itself would already be done by
that time (instantly)...
Paulo
On Fri, Jan 3, 2025 at 9:32 AM bengalack ***@***.***> wrote:
It is unclear to me how, or if, we can set correct execution speed on the
command part of the VDP. It seems like it does things immediately by
default? I'm reliant on the copy command being executed over time, and not
instanltly, so I'd like to know how this can be achieved.
—
Reply to this email directly, view it on GitHub
<#109>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFOLICTUWC32NGBUYFBTK32IZ7ORAVCNFSM6AAAAABURTZ3FCVHI2DSMVQWIX3LMV43ASLTON2WKOZSG43DONJQGIZTMMI>
.
You are receiving this because you are subscribed to this thread.
It is unclear to me how, or if, we can set correct execution speed on the command part of the VDP. It seems like it does things immediately by default? I'm reliant on the copy command being executed over time, and not instanltly, so I'd like to know how this can be achieved.
The text was updated successfully, but these errors were encountered: