Replies: 2 comments
-
Yes, that is perfectly fine, at least for What I do is have a class that derives from |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thank you Andre. I was thinking along the same lines. I'll discover nodes
on the network with a network class and then create od objects as needed as
it instantiates each node, passing the od to the constructor as you mention.
Thanks!
…On Sun, Jan 29, 2023, 9:07 PM André Colomb ***@***.***> wrote:
Yes, that is perfectly fine, at least for RemoteNode objects. I don't
know how the local node classes interact with it, but it doesn't make much
sense to create several of those with a common OD usually.
What I do is have a class that derives from RemoteNode, with the OD of
the specific device model as a class variable loaded once during the class
definition. Each instance then refers to the common object by passing it to
the parent class constructor during initialization.
—
Reply to this email directly, view it on GitHub
<#344 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHVSC5NVGQXEGFW3JVOI2LWU5EA5ANCNFSM6AAAAAAUKPU6CI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have dozens of nodes that share an EDS. Can I safely create one ObjectDictionary object and pass it to all the objects? From what I can see the OD is read only but I want to make sure.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions