Hello,
in a dynamic GUI patching project, I'm using a bang that would destroy itself and some other objects that come along with it. [bang] is dynamically contructed then bang would need a callback abstraction, or a 'settable receive'.
Maybe such thing would be possible by using a slider instead of a bang, and setting max and min value to a number attributed to this graphical element, but it makes more sense graphicaly to use a bang for that, we know that bang doesn't output anything else than 'bang', so my question is: why not telling [bang] to output a message, and using only 'bang' for default?
Colet Patrice
Hi,
Try making an abstraction with graph-on-parent enabled and make it the same size as the bang. Then you can tweak whatever you want inside, use creation arguments (even on the bang)... I'm using this trick to do synchronized GUI objects. The only problem is you can't access the properties menu, but you can still modify the bang if you send it messages like size, color... It works great for me! Also, if you make the graph-on-parent 2 pixels wider you will get a kind of "bold" bang, which I find very cool.
Cheers,
Quim
2012/6/20 Patrice Colet colet.patrice@free.fr
Hello,
in a dynamic GUI patching project, I'm using a bang that would destroy itself and some other objects that come along with it. [bang] is dynamically contructed then bang would need a callback abstraction, or a 'settable receive'.
Maybe such thing would be possible by using a slider instead of a bang, and setting max and min value to a number attributed to this graphical element, but it makes more sense graphicaly to use a bang for that, we know that bang doesn't output anything else than 'bang', so my question is: why not telling [bang] to output a message, and using only 'bang' for default?
Colet Patrice
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
That is interesting, in fact, I've alreading made a project like this, a sequencer using one gop per step, I don't think I will do this anymore, I hate waiting so long when a patch is loading, ;).
Also this trick is like creating a callback abstraction along with the bang that is mapping send name, no need for GOPs to do this.
In fact I don't use gops at all, neither abstractions, only dynamic patching messages.
The purpose of my project is about managing this interface with lesser objects as possible
Colet Patrice
----- Mail original -----
De: "Quim Llimona" lemonzi42@gmail.com À: "Patrice Colet" colet.patrice@free.fr Cc: "pd-list" pd-list@iem.at Envoyé: Mercredi 20 Juin 2012 08:44:14 Objet: Re: [PD] send a message with IEM/bang
Hi,
Try making an abstraction with graph-on-parent enabled and make it the same size as the bang. Then you can tweak whatever you want inside, use creation arguments (even on the bang)... I'm using this trick to do synchronized GUI objects. The only problem is you can't access the properties menu, but you can still modify the bang if you send it messages like size, color... It works great for me! Also, if you make the graph-on-parent 2 pixels wider you will get a kind of "bold" bang, which I find very cool.
Cheers,
Quim
2012/6/20 Patrice Colet colet.patrice@free.fr
Hello,
in a dynamic GUI patching project, I'm using a bang that would destroy itself and some other objects that come along with it. [bang] is dynamically contructed then bang would need a callback abstraction, or a 'settable receive'.
Maybe such thing would be possible by using a slider instead of a bang, and setting max and min value to a number attributed to this graphical element, but it makes more sense graphicaly to use a bang for that, we know that bang doesn't output anything else than 'bang', so my question is: why not telling [bang] to output a message, and using only 'bang' for default?
Colet Patrice
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
I don't need to access properties menu, this part of the patch should never be in edit mode, so your solution is so far so good.
Colet Patrice
----- Mail original -----
De: "Quim Llimona" lemonzi42@gmail.com À: "Patrice Colet" colet.patrice@free.fr Cc: "pd-list" pd-list@iem.at Envoyé: Mercredi 20 Juin 2012 08:44:14 Objet: Re: [PD] send a message with IEM/bang
Hi,
Try making an abstraction with graph-on-parent enabled and make it the same size as the bang. Then you can tweak whatever you want inside, use creation arguments (even on the bang)... I'm using this trick to do synchronized GUI objects. The only problem is you can't access the properties menu, but you can still modify the bang if you send it messages like size, color... It works great for me! Also, if you make the graph-on-parent 2 pixels wider you will get a kind of "bold" bang, which I find very cool.
Cheers,
Quim
2012/6/20 Patrice Colet colet.patrice@free.fr
Hello,
in a dynamic GUI patching project, I'm using a bang that would destroy itself and some other objects that come along with it. [bang] is dynamically contructed then bang would need a callback abstraction, or a 'settable receive'.
Maybe such thing would be possible by using a slider instead of a bang, and setting max and min value to a number attributed to this graphical element, but it makes more sense graphicaly to use a bang for that, we know that bang doesn't output anything else than 'bang', so my question is: why not telling [bang] to output a message, and using only 'bang' for default?
Colet Patrice
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-06-20 00:26, Patrice Colet wrote:
Hello,
in a dynamic GUI patching project, I'm using a bang that would destroy itself
"destroying itself" is soemthing that Pd helps a lot with: if you have an object destroy itself, Pd will destroy itself as well. iemgut's [canvasdelete] can help you.
and some other objects that come along with it. [bang] is
do you mean [bng] or [bang]?
dynamically contructed then bang would need a callback abstraction, or a 'settable receive'.
[bng] does have a settable-receive.
fgasdrm IOhannes
I don't think there is a need in iemguts for that, in attached example we see a bang destroying itself by clearing the patch, it's working perfectly, many other features that should work, particulary in pdx, are full of bugs indeed (see edit mode message is not working anymore unless it has been corrected), but not this one.
If I have several other [bng] in this subpatch, and want to rebuild all the objects that have been cleared, but not the one where I clicked, I would need to know which bang have been clicked, and it's not possible without creating a subpatch that is mapping the new created bang to an individual name, but if bang is sending a message, this problem, and certainly many other problems like this would go away.
Colet Patrice
----- Mail original -----
De: "IOhannes m zmoelnig" zmoelnig@iem.at À: pd-list@iem.at Envoyé: Mercredi 20 Juin 2012 12:13:37 Objet: Re: [PD] send a message with IEM/bang
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-06-20 00:26, Patrice Colet wrote:
Hello,
in a dynamic GUI patching project, I'm using a bang that would destroy itself
"destroying itself" is soemthing that Pd helps a lot with: if you have an object destroy itself, Pd will destroy itself as well. iemgut's [canvasdelete] can help you.
and some other objects that come along with it. [bang] is
do you mean [bng] or [bang]?
dynamically contructed then bang would need a callback abstraction, or a 'settable receive'.
[bng] does have a settable-receive.
fgasdrm IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk/hok0ACgkQkX2Xpv6ydvRhoQCgzcDKaXdVcoiqjnDq5ddrugMZ 9hYAn26dCKtRu1ioSwZS2m8JxHsVt27g =fBvm -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-06-20 13:42, Patrice Colet wrote:
I don't think there is a need in iemguts for that, in attached example we see a bang destroying itself by clearing the patch, it's working perfectly, many other features that should work, particulary in pdx, are full of bugs indeed (see edit mode message is not working anymore unless it has been corrected), but not this one.
i can confirm that it does not crash. after a quick glance (not having looked at the code) i think this is some black magic in [bng]...:-)
fgamdr IOhannnes
-
IOhannes m zmoelnig -
Patrice Colet -
Quim Llimona