Em qua., 1 de dez. de 2021 às 17:44, Miller Puckette via Pd-list <
pd-list@lists.iem.at> escreveu:
> I think having a "message" object is a better idea. Only thing is, it
> does raise some interesting design questions of its own - like, what of
> sending more than one message; how to specify
well, done, removed.
Now, one last message isn't documented yet, the "sort" message, used in
Data Structures. This comes up first at example 7.sequencer in the data
structures examples, but we don't have any explanation why it happens. And
the message is called multiple times, maybe in
On 12/1/21 19:55, Csaba Láng wrote:
Nothin at all, just have to replace all in my patches :)
no.
[gemgflw3window] is *not* a replacement for [gemwin].
it's a replacement for [gemcocoawindow].
both (and all the other [gem*window]) objects are one of the building
blocks for [gemwin].
* IOhannes m zmölnig [2021-11-30 20:18]:
> Am 30. November 2021 19:50:29 MEZ schrieb "Csaba Láng" :
> >Dear list,
> >
> >is there a fix already on this issue?
> >https://github.com/umlaeute/Gem/issues/257
> >
> >or i have to use [gemglfw3window] and we have to live with it.
> >
>
>
> What is
If you don't send [map 0, map 1( to the parent canvas, the graph will
still contain previous graphical elements. You don't notice this if you
use a mycanvas in the background, though.
On 01.12.2021 22:04, Alexandre Torres Porres wrote:
yeah, I'll just take the 'coords' message out and keep
yeah, I'll just take the 'coords' message out and keep the rest
but it's not like it always needs map 0/1, does it?
Em qua., 1 de dez. de 2021 às 18:03, Christof Ressi
escreveu:
> The problem with [coords( is that you also need to do [map 0, map1( to
> force a redraw of the parent canvas. This
The problem with [coords( is that you also need to do [map 0, map1( to
force a redraw of the parent canvas. This means you would have to
document [map( as well.
I would say don't document it for now and instead let's hope that we
will *finally* get
I think having a "message" object is a better idea. Only thing is, it
does raise some interesting design questions of its own - like, what of
sending more than one message; how to specify destination names without
using the ';' separator, and what if we allowed expressions ...
cheers
Miller
On
what if we introduce double dollar syntax to grab patch arguments?
Actually, I already thought about that. The problem is that "$" is only
interpreted as a dollar or dollarsym if it is followed by a number. So
currently "$$" is not a reserved token, meaning that "$$" is a valid
symbol. We
I like the idea.
Em qua., 1 de dez. de 2021 às 17:14, José de Abreu
escreveu:
> I have an idea about $0
>
> what if we introduce double dollar syntax to grab patch arguments? and
> then inside messages $$1 would be first abstraction argument, while $1 is
> the the first element of the list (as
I have an idea about $0
what if we introduce double dollar syntax to grab patch arguments? and then
inside messages $$1 would be first abstraction argument, while $1 is the
the first element of the list (as it already is)
this way, $$0 in a message would be what $0 is for an object, $$1 would be
sorry to insist, but this has been already committed to my documentation
branch and it's the only big change that I really worry about. So let's
settle this before it's too late :)
thanks
Em sáb., 27 de nov. de 2021 às 22:28, Alexandre Torres Porres <
por...@gmail.com> escreveu:
> I updated my
Nothin at all, just have to replace all in my patches :)
On Tue, Nov 30, 2021 at 8:16 PM IOhannes m zmölnig wrote:
> Am 30. November 2021 19:50:29 MEZ schrieb "Csaba Láng" <
> langcs...@gmail.com>:
> >Dear list,
> >
> >is there a fix already on this issue?
>
13 matches
Mail list logo
