-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
some cyclone's objects don't resize #223
Comments
note for later: this is caused by way embed works in a saved patch and we need a figure out a way of getting the zooming parameter and adding that to how these objects are saved |
can you elaborate? :) |
kinda fuzzy on this, but like basically embed saves data in the patch right? like how arrays get saved and structs get saved and what not. these cyclone objects that save data, we have our own special way of storing and recalling data,.. i think,.. but this was pre-resizing abilities in pure data, and resize data also gets saved in the patch obv, so this is why these cyclone objects that save data don't resize, we need to relook at how these cyclone objects save data with the patch and account for these "new" resizing parameters that also get saved in the patch. |
yeah, the embed info gets parsed to "hammerfile_new" here https://github.com/porres/pd-cyclone/blob/master/shared/common/file.c#L803 and also in "hammerfile_setup". well, I'm not sure how to follow up on this one, do you think you can develop on this anytime @derekxkwan ? |
hmm, so it looks like the resizing appears in the save file following the object and its data as
the 2 here means the array object gets resized to 2 characters wide (and when we don't resize or resize back to original size, the when i try resizing [coll], this |
note: to get the width, the t_object x_ob in the _coll struct has it, so wherever it gets passed around, you can access it by |
[coll], [table], [prob], and [funbuff] can be resized but this is not saved in the patch when you reopen it - this is because they use 'embed' - this is better described below by Derek.
The text was updated successfully, but these errors were encountered: