You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The whole thing started out with me misguessing the function of the reset message to a fluid.dataset~. I was experimenting with the refermessage (to avoid excessive copying) but then I wanted a way "derefer" a dataset on the actual fluid.dataset~ object at hand. I guessed reset would just reset the object like a delete & undo would, but instead it seems to rename the dataset while keeping its contents.
While I was trying to "reset" the dataset objects with an actual delete & undo I discovered a consistent Max crash (upon undo/reopen). See attached patch: refer_bug.maxpat.zip
It is probably an edge-case, but since it is consistent, I thought I should report it.
I noticed issue #249 and @jamesb93 helped me understood how reset is not what I thought it would be. We have also discussed the idea of having refer without arguments to do the dereferencing (that feels like the Maxish way). Right now I can achieve the dereferencing safely if I provide an empty dataset "dedicated" to this purpose. This is still much less overhead (and horror) than my current method of patch-scripting the fluid.dataset~ object with the target name as a way of "referring caveman-style". :))
The text was updated successfully, but these errors were encountered:
The whole thing started out with me misguessing the function of the
reset
message to afluid.dataset~
. I was experimenting with therefer
message (to avoid excessive copying) but then I wanted a way "derefer" a dataset on the actualfluid.dataset~
object at hand. I guessedreset
would just reset the object like a delete & undo would, but instead it seems to rename the dataset while keeping its contents.While I was trying to "reset" the dataset objects with an actual delete & undo I discovered a consistent Max crash (upon undo/reopen). See attached patch: refer_bug.maxpat.zip
or
It is probably an edge-case, but since it is consistent, I thought I should report it.
I noticed issue #249 and @jamesb93 helped me understood how
reset
is not what I thought it would be. We have also discussed the idea of havingrefer
without arguments to do the dereferencing (that feels like the Maxish way). Right now I can achieve the dereferencing safely if I provide an empty dataset "dedicated" to this purpose. This is still much less overhead (and horror) than my current method of patch-scripting thefluid.dataset~
object with the target name as a way of "referring caveman-style". :))The text was updated successfully, but these errors were encountered: