Hi!
Are you using the latest `master` version? sync was a boolean until 1.4.x
and was switched to a string in the current development branch.
Romain
Le sam. 29 févr. 2020 à 05:36, Per Gunnarsson <mustafe...@gmail.com> a
écrit :
> Hello!
>
> I tried the documentation on clock.assign_new, but it didn' work.
>
> After trying:
> clock.assign_new(sync="none",
> clock.assign_new(sync=none,
> clock.assign_new(sync="false",
>
> I tried:
>
> clock.assign_new(sync=false,
>
> The last try seems to work.
>
> The API doc says:
> clock.assign_new
>
> Create a new clock and assign it to a list of sources.
>
> Type:
>
> (?id : string, ?sync : string, [source('a)]) -> unit
>
> Arguments:
>
> - id (of type string, which defaults to ""): Identifier for the new
> clock. The default empty string means that the identifier of the first
> source will be used.
> - sync (of type string, which defaults to "auto"): Synchronization
> mode. One of: "auto", "cpu", or "none".
> - (unlabeled) (of type [source('a)]): List of sources to which the new
> clock will be assigned
>
> _______________________________________________
> Savonet-users mailing list
> Savonet-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users
