Support for VirtualMachine.networkDevices about vz HOT 9 OPEN

@balajiv113 Thanks for creating a new issue!
I didn't know that! Thanks.

I will work for it in Sat (JST) because I'm a little busy 🙏

from vz.

I'm sorry too late.

This is a delegate method which meant that the method will be held by a different object than VZVirtualMachine, which has VZVirtualMachine as a property. So I may take a little time to design...

from vz.

Note that this understanding is wrong. They are not dependent on each other.

Support for VirtualMachine.networkDevices. With this support, we can use attachmentWasDisconnectedWithError to understand

Here is a good example. I use the delegate to use the GUI; the object we specify for delegate is not a VZVirtualMachine object.

from vz.

This is one idea, although the long method names are annoying.

vm, err := vz.NewVirtualMachine(config)
if err != nil {
  return err
}

vm.WatchNetworkDeviceAttachmentWasDisconnected(func(networkDevice *vz.NetworkDevice, err error) {
  // Do something here...
})

vm.Start()

from vz.

@balajiv113 Do you have any idea about this method signature?

from vz.

@Code-Hex you mean the signature of attachmentWasDisconnectedWithError ??

from vz.

@balajiv113 Yes, I think this usage is may difficult 🤔
#118 (comment)

from vz.

True but this was better compared to creating delegate object as a whole in go.

This will be extensible as well when new methods comes up as far as i see. Internally we will manage the delegate and users doesn't have to know much about it.

One thing to watch out is, we need to support both this and GUI delegate.

from vz.

@balajiv113 Thanks.

Yeah I think so :D

One thing to watch out is, we need to support both this and GUI delegate.

from vz.