2019.30790 - WebClient DAT - Asynchronous par problems

Bugs
1

Hello,

It seems like there is a problem with the Asynchronous parameter in the WebClient DAT.

  1. You can’t drag and drop it in the custom parameters window like with other parameters to automate custom parameter creation process.
  2. If you create a toggle custom parameter and try to bind it with the Async parameter of the WebClient DAT, an expression similar to a reference will appear and the parameter will turn red. (see attached image)

To reproduce 1. simply drop the WebClient DAT in a custom component (base) and try to create the parameter on the newly created Base COMP with a drag and drop.

To reproduce 2. simply create a custom parameter (type toggle) on a Base COMP and try to make a binding from the Base COMP to the WebClient DAT Async parameter.

Thank you for your time,
Michel

WebClientDAT_async_bug.png
WebClientDAT_async_bug.png955×1023 40.2 KB

2

RE:

I believe it is because “async” is a keyword used in Python ?

If I do the regular:

op('webclient1').par.async = par.eval()
in a parexec DAT, I will get an error.

If I replace that line by:

setattr(op('webclient1').par, 'async', par.eval())
it is working fine.

3

Yeah, that’s why. This didn’t occur to me when I was adding the Web Client DAT at the time – I’ll change it to something Python accepts. Web DAT got around this by doing ‘asyncfetch’ instead of ‘async’. I’ll do something similar.

Thanks for the report.