Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Format does not allow a null Address value when using a Timestamped<HarpMessage> overload #71

Open
bruno-f-cruz opened this issue Sep 1, 2023 · 0 comments

Comments

@bruno-f-cruz
Copy link
Contributor

The Format operator effectively implements the ability of modifying specific parts of an harp message. For instance, all messages coming from a device, can be modified to always have an address = 20 by:

image

One can use the same concept to "inject" timestamps into other harp messages. For instance:

image

However, when one tries to combine the two approaches (which could be potentially very useful to generate harp virtual devices), by setting the "address" property to null, the following error is thrown:

No message address is specified

@bruno-f-cruz bruno-f-cruz changed the title Format does not allow a Address null value when using a Timestamped<> overload Format does not allow a Address null value when using a Timestamped<T> overload Sep 3, 2023
@bruno-f-cruz bruno-f-cruz changed the title Format does not allow a Address null value when using a Timestamped<T> overload Format does not allow a null Address value when using a Timestamped<T> overload Sep 7, 2023
@glopesdev glopesdev changed the title Format does not allow a null Address value when using a Timestamped<T> overload Format does not allow a null Address value when using a Timestamped<HarpMessage> overload Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant