On Thu, 16 Aug 2007, marius schebella wrote:
I would give most priority to any kind of $0 feature in messages. and
then the next step for me would be to differentiate between $-variables
(in messages) and # or ? or @ variables in patches. that way you would
not break backwards compatibility,
On Fri, 17 Aug 2007, Matteo Sisti Sette wrote:
2) I guess it may imply some implementation difficulties, since in the
patch file $'s are actually saved as #'s
(indeed there's even a bug that if you open a slider/toggle's properties and
it has a property with some $'s inside its name other than
Hallo,
marius schebella hat gesagt: // marius schebella wrote:
I don't know how easy/difficult an implementation of new variable names
would be. I would give most priority to any kind of $0 feature in messages.
and then the next step for me would be to differentiate between
$-variables (in
Mathieu Bouchard wrote:
On Thu, 16 Aug 2007, marius schebella wrote:
I would give most priority to any kind of $0 feature in messages. and
then the next step for me would be to differentiate between
$-variables (in messages) and # or ? or @ variables in patches. that
way you would not
On Fri, 17 Aug 2007, marius schebella wrote:
even with a combination of charactars $$ ## #$ $# @@ ?? you can't be sure
that they are not used before.
Right. For example,
http://www.localarcade.com/arcade_art/data/thumbnails/2/q-bert.jpg
_ _ __ ___ _ _
Mathieu Bouchard wrote:
On Fri, 17 Aug 2007, marius schebella wrote:
even with a combination of charactars $$ ## #$ $# @@ ?? you can't be
sure that they are not used before.
Right. For example,
http://www.localarcade.com/arcade_art/data/thumbnails/2/q-bert.jpg
to make it more clear u
How does the 4 digit number get assigned to $0? I have always been
curious about this.
Kevin
On 8/16/07, Matteo Sisti Sette [EMAIL PROTECTED] wrote:
marius schebella wrote:
it is a pity that there is no $0 in messages. that would help so much!
I use local send/receive like s $0-blabla.
Matteo Sisti Sette wrote:
The only way of introducing such a facility without breaking
backward-compatibility (or is it forward?), would be to introduce a third
symbol, say @ (well it should be one that is currently not allowed in
messages): @n if used inside a message, would refer to the
the first appearance of $0 is substituted by 1000, the next with 1001
and so on.
marius.
Kevin McCoy wrote:
How does the 4 digit number get assigned to $0? I have always been
curious about this.
Kevin
On 8/16/07, Matteo Sisti Sette [EMAIL PROTECTED] wrote:
marius schebella wrote:
it
marius schebella wrote
why not use # as in max? @ is already used to access object attributes.
marius.
# may be a good option, but:
1) It would not be as in max, it would be viceversa (max uses # for creation
arguments and $ for message arguments)
2) I guess it may imply some implementation
I don't know how easy/difficult an implementation of new variable names
would be. I would give most priority to any kind of $0 feature in messages.
and then the next step for me would be to differentiate between
$-variables (in messages) and # or ? or @ variables in patches. that way
you would
On Thu, 16 Aug 2007, Kevin McCoy wrote:
How does the 4 digit number get assigned to $0? I have always been
curious about this.
It's a special case in the program. It comes from the canvas environment,
which exists for every non-subpatch canvas. Every such canvas gets a new
number. it
12 matches
Mail list logo
