Hi,
I have a small problem: If I create a HDA by compilation of a VFL file, I have limitations use the “#pragma callback”. I can use only hscript, because I can't switch between “hscript” and “python” for my callback script.
If I need to use python, I use workaround for it. For example, I have a VFL file and I want use python for callback:
I write:
…
#pragma label clr “Color”
#pragma hint clr color
#pragma callback clr “myCallback.cmd”
…
Next I should write hscript for callback:
…
python -c “import myLib”;
python -c “myLib.run(hou.pwd())”;
…
That works for now, but it is not handy.
I would like to ask developers - are you going to add the #pragma for description script language to interpret the “callback script”?

archie
Hi,
I have a small problem: If I create a HDA by compilation of a VFL file, I have limitations use the “#pragma callback”. I can use only hscript, because I can't switch between “hscript” and “python” for my callback script.
If I need to use python, I use workaround for it. For example, I have a VFL file and I want use python for callback:
I write:
…
#pragma label clr “Color”
#pragma hint clr color
#pragma callback clr “myCallback.cmd”
…
Next I should write hscript for callback:
…
python -c “import myLib”;
python -c “myLib.run(hou.pwd())”;
…
That works for now, but it is not handy.
I would like to ask developers - are you going to add the #pragma for description script language to interpret the “callback script”?

It took me a little while to uncover this, but you should be able to do:

#pragma parmtag clr script_callback_language python


We'll make sure this gets documented.

Hi Mark!
Thank you very much for your quick response. This works well!