Hi, looking for a vanilla "grid" like object, a while ago on this list, [touch] was presented as so. I tried downloading the abstractions from http://www.droidparty.net/ but I couldn't run the object on Pd 0.48-1, it just looks like a normal non graphical subpatch, anybody else get this?
anyway, the quest for vanilla like grid objects continues
thanks
Hi Alexandre,
On 02/03/18 05:09, Alexandre Torres Porres wrote:
this?
I had noticed this too - all droidparty abstractions don't work in recent Pd versions - but didn't yet find time to:
My hunch is Miller or somebody changed something with the unsupported donecanvasdialog messages that those droidparty abstractions are (ab)using, but I do not have evidence for this yet.
Will report back here if I get some time to examine this.
anyway, the quest for vanilla like grid objects continues
If Pd's canvas object had the following property it would enable much more powerful GUIs to be built by non-developers: report all clicks, even in a GOP subpatch, even when not in edit mode.
Cheers,
Chris.
indeed, for what i know, "donecanvasdialog" changed with 0.48 ! (there has been a post on this list by christof ressi some months ago) https://www.mail-archive.com/pd-list@lists.iem.at/msg12504.html
the third argument (the one that represents the "graph on parent" and "hide object names and arguments" checkboxes) has changed its counting method.
what used to be "2" in earlier PD versions (both checkboxes ticked) must now say "3":
so until PD 0.47 it was: donecanvasdialog 1 -1 2 0 -1 1 1 120 60 10 10, dirty 0
from PD 0.48 on it's: donecanvasdialog 1 -1 3 0 -1 1 1 120 60 10 10, dirty 0
that broke my GOP patches too, but i already updated them all accordingly. not too much work ...
but i really think this should be mentioned in capital letters in the release notes for PD 0.48, since i'm sure many people "exploited" this feature to build their customized GUIs
best
oliver
this argument actually is a bitfield where the first bit is "graph on parent" and the second bit is "hide object name". the people who first experimented with dynamic patching exploited a bug (maybe unintentionally) in the [donecanvasdialog( message handling where 2 would be treated the same as 3. since then, most people just copied it. the correct value has always been 3 (= both bits set). Miller thought about adding a compatibily argument but apparently decided against it: https://lists.puredata.info/pipermail/pd-list/2017-07/119724.html
I agree with oliver that we should spread the word about this bugfix since it affects quite a number of patches. I'll post it to facebook group.
please, what do these numbers/argument mean again? quite explicitly?
what are the options, what is 0, 1, 2, 3? Are there more? What used to be "2"? What is "2" now?
Is there any documentation about this out there, what is this used for in dynamic patching?
thanks
2018-03-02 13:50 GMT-03:00 Christof Ressi christof.ressi@gmx.at:
On 03/03/18 00:50, Christof Ressi wrote:
Excellent, thanks for the explanation!
Cheers,
Chris.