Hi all,

I have a custom vex function to install into Houdini.
Here is the process.
1.I use hcustom to compile function.C.
the compilation is done without bugs reported.
2.The file function.so are automatically moved to directory under ~/houdiniX.Y/dso
3.According to the description in the introduction page (last few lines)
http://www.sidefx.com/docs/hdk12.1/hdk_vexop.html [sidefx.com]
I add a text file VEXdso in folder ~/houdiniX.Y/vex
the content of VEXdso has only one line
function.so

I thought Houdini can find my custom vex function now, but it didn't.
Is there anything wrong in my settings?

Thanks.

Hi,

I found that once the file “test_func.so” was put into ~/houdiniX.Y/dso
The function can work properly.

But in the script dialog, when I type ‘test_func()’, the dialog still
can not recognize it.
(for example, if I type 'near", there should be a prompt box showing nearpoint())
I think there should be a right way to set VEXdso file.
Did any one familiar with this?

Nope, I don't think there is a single place in Houdini GUI, which understand VEX syntax nor “intellisense” on its functions. Thankfully VEX is still executed by Houdini's nodes . Syntax coloring and other hints come from hscript, not VEX, so you won't see your functions listed anywhere beside VEX compiler itself. You can check it with command line:

vcc -X sop | grep test_func

- where “sop” is a context name the function was registered for. Also hscript command:

dsoinfo -qv

prints details about custom loaded vex extensions.

hth,
skk.

Thanks, SYmek.

Did you mean that no way to do syntax coloring and hints for custom vex function?

pyrochlore
Thanks, SYmek.
Did you mean that no way to do syntax coloring and hints for custom vex function?

Afaik there is no way to do syntax coloring nor hints for any vex, not just custom. I know, it's insane! I think most people use external editor anyway. I usually use C coloring, although to some of them there are color schemes for Vex (search forums).