cruiserandmax

I'm interested in building a stroke tool that associates the frame number at which a stroke was drawn with the primitive of the stroke. It seems like stroke meta data maybe a good way to handle this, but following the docs it doesn't seem to work.

Does anyone have an example of setting custom data per stroke, and doing something with it after the stroke node inside the hda?

I have tried making an hda with just a stroke node inside, setting the hda Node Default State to stroke, dragging the Number of Strokes parameter from the parameters panel on the stroke node inside the hda to the Edit Operator Type Properties Parameters panel of the hda. Then adding a new parameter on the hda properties called something like stroke#_frame or stroke_frame#. According to the docs the Meta Data parameter on the stroke geometry node:

"Stores the values of all parameters whose names start with stroke_ from the top level node. These are copied into correspondingly named primitive attributes."

But the Meta Data always seem to contain just a list like
I can't figure out what I am doing wrong?

We are in a situation where we have a SOP HDA, say foo.hda, that exists without any versions. However that same foo.hda exists in our HOUDINI_OTLSCAN_PATH in a lower priority path location where it happens to have a foo.hda::2 version which is significantly different from the foo.hda definition in the priority scan path location. As a result whenever we TAB create this SOP HDA in a houdini session using this HOUDIN_OTLSCAN_PATH we get the foo.hda::2 defined in the lower priority location... And if we then switch the asset definition to the foo.hda version it does appear to switch to the priority source location for the .hda file, however it continues to display the parameter interface that was defined in the foo.hda::2 definition which makes things very confusing.

Is there any way to get houdini to correctly resolve to the foo.hda definition (including parameter interface) that is defined in the first folder of the HOUDINI_OTLSCAN_PATH?

Is there any way to setup a SOP HDA so that when the <ENTER> key is used (to enter "edit" mode) the edit mode of a targeted SOP within the HDA becomes active for use?