Brennon Bortz

I'm having a problem setting the value of a message box. I'm accomplishing what I need to do, but I'm quite sure that my approach is not the best. I need to be able to dynamically update the contents of a message box that can be banged out in a format appropriate for a line object (i.e., "0., 6.931024 15000"). In fact, this is exactly the message I need, and I need to be able to update the duration.

I tried simply a message box with "set 0., 6.931024 $1", but this includes the backslash in the message box being set. Without the backslash, the comma is not escaped and the receiving message box is set to "0."

In the following patch, you can see how I've finagled it to work, but I would appreciate any insight on how to accomplish this more appropriately, efficiently, elegantly, etc.

I'm having a problem setting the value of a message box.  I'm accomplishing what I need to do, but I'm quite sure that my approach is not the best.  I need to be able to dynamically update the contents of a message box that can be banged out in a format appropriate for a line object (i.e., "0., 6.931024 15000").  In fact, this is exactly the message I need, and I need to be able to update the duration.

I tried simply a message box with "set 0., 6.931024 $1", but this includes the backslash in the message box being set.  Without the backslash, the comma is not escaped and the receiving message box is set to "0."

problems-setting-message

Quote: Brennon Bortz wrote on Tue, 08 January 2008 21:57

----------------------------------------------------

> I'm having a problem setting the value of a message box. I'm accomplishing what I need to do, but I'm quite sure that my approach is not the best. I need to be able to dynamically update the contents of a message box that can be banged out in a format appropriate for a line object (i.e., "0., 6.931024 15000"). In fact, this is exactly the message I need, and I need to be able to update the duration.

Quote: Brennon Bortz wrote on Tue, 08 January 2008 21:57
----------------------------------------------------
> I'm having a problem setting the value of a message box.  I'm accomplishing what I need to do, but I'm quite sure that my approach is not the best.  I need to be able to dynamically update the contents of a message box that can be banged out in a format appropriate for a line object (i.e., "0., 6.931024 15000").  In fact, this is exactly the message I need, and I need to be able to update the duration.
>
>
----------------------------------------------------


> In the following patch, you can see how I've finagled it to work, but

> I would appreciate any insight on how to accomplish this more

> appropriately, efficiently, elegantly, etc.

You have to know what the comma does. This question is coming up a lot 

on the list. Usually there is no initial mentioning of the purpose, but 

its always the wish to drive a line or line~ object. If you get yourself 

to ask how to achieve the real purpose, you'd probably find out yourself 

Beside the sprintf solution mentioned, (which is more confusing for a 

beginner than a message box with a comma... ;-) there are several ways 

to drive a line, the easiest is the message box with a comma by the way...

Brennon Bortz schrieb:
> In the following patch, you can see how I've finagled it to work, but
> I would appreciate any insight on how to accomplish this more
> appropriately, efficiently, elegantly, etc.

You have to know what the comma does. This question is coming up a lot 
on the list. Usually there is no initial mentioning of the purpose, but 
its always the wish to drive a line or line~ object. If you get yourself 
to ask how to achieve the real purpose, you'd probably find out yourself 
easier as well...

Beside the sprintf solution mentioned, (which is more confusing for a 
beginner than a message box with a comma... ;-) there are several ways 
to drive a line, the easiest is the message box with a comma by the way...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com

> there are several ways to drive a line, the easiest is the message

Stefan Tiedje schrieb:
> there are several ways to drive a line, the easiest is the message
> box with a comma by the way...

Quote: Stefan Tiedje wrote on Tue, 08 January 2008 23:41

Thanks for your help. If I understand your comments and patches correctly, I believe you're trying to point out that the comma breaks a message into multiple successive messages, which I do understand. However, what I'm trying to do is reset the contents of a single message to such a compound message, including the comma. As one with programming experience, the sprintf object makes perfect sense to me, and I now notice that it is referenced in the help file for the message object--please forgive my hastiness. This same experience is what led me to believe that escaping the comma in the "set" message with a backslash character would avoid its literal interpretation in the "set" message.

Nonetheless, you seem to hint that there is more than one way to skin the proverbial cat, but your patch is only showing several ways to drive a line--which isn't exactly what I'm trying to do. Is there another way to format the message which will in turn drive the line? If sprintf is the best way to go, however, this cat is done skunned.

Quote: Stefan Tiedje wrote on Tue, 08 January 2008 23:41
----------------------------------------------------

Thanks for your help.  If I understand your comments and patches correctly, I believe you're trying to point out that the comma breaks a message into multiple successive messages, which I do understand.  However, what I'm trying to do is reset the contents of a single message to such a compound message, including the comma.  As one with programming experience, the sprintf object makes perfect sense to me, and I now notice that it is referenced in the help file for the message object--please forgive my hastiness.  This same experience is what led me to believe that escaping the comma in the "set" message with a backslash character would avoid its literal interpretation in the "set" message.

Nonetheless, you seem to hint that there is more than one way to skin the proverbial cat, but your patch is only showing several ways to drive a line--which isn't exactly what I'm trying to do.  Is there another way to format the message which will in turn drive the line?  If sprintf is the best way to go, however, this cat is done skunned.

> Is there another way to format the message which will in turn drive

> the line? If sprintf is the best way to go, however, this cat is done

It depends, if you really need a changing message box with a comma in 

However, for driving a line you don't need a message box at all. (See 

But a message box with several $1, $x replacements is a convenient way 

to massage messages, including existing commas...

(f.e. [pack f f f]->[$1, $2 $3] for a line control...)

I just don't know why you want to change the content of the message box 

itself, but I am sure you have a reason...

Brennon Bortz schrieb:
> Is there another way to format the message which will in turn drive
> the line? If sprintf is the best way to go, however, this cat is done
> skunned.

It depends, if you really need a changing message box with a comma in 
it, sprintf is fine.
However, for driving a line you don't need a message box at all. (See 
the trigger example).
But a message box with several $1, $x replacements is a convenient way 
to massage messages, including existing commas...
(f.e. [pack f f f]->[$1, $2 $3] for a line control...)

I just don't know why you want to change the content of the message box 
itself, but I am sure you have a reason...

Quote: Stefan Tiedje wrote on Wed, 09 January 2008 03:14

---------------------------------------------------- 

> I just don't know why you want to change the content of the message box 

> itself, but I am sure you have a reason...

Only to save myself the time of reworking a boatload of subpatches. Next time I'll know better!

Quote: Stefan Tiedje wrote on Wed, 09 January 2008 03:14
---------------------------------------------------- 
> I just don't know why you want to change the content of the message box 
> itself, but I am sure you have a reason...
>

Only to save myself the time of reworking a boatload of subpatches.  Next time I'll know better!

Quote: Brennon Bortz wrote on Wed, 09 January 2008 22:57

> Quote: Stefan Tiedje wrote on Wed, 09 January 2008 03:14

> ---------------------------------------------------- 

> > I just don't know why you want to change the content of the message box 

> > itself, but I am sure you have a reason...

> Only to save myself the time of reworking a boatload of subpatches. Next time I'll know better!

It has also come up recently that this message to line:

I'd ditch the comma entirely, and work with a simpler message.

Quote: Brennon Bortz wrote on Wed, 09 January 2008 22:57
----------------------------------------------------
> Quote: Stefan Tiedje wrote on Wed, 09 January 2008 03:14
> ---------------------------------------------------- 
> > I just don't know why you want to change the content of the message box 
> > itself, but I am sure you have a reason...
> >
>
> Only to save myself the time of reworking a boatload of subpatches.  Next time I'll know better!
>
> Thanks Stefan,
> Brennon
----------------------------------------------------

>It has also come up recently that this message to line:

>I'd ditch the comma entirely, and work with a simpler message.

I think that's only true for line~ (which understands lists of time/level pairs), but not for line.

Chris Muir | "There are many futures and only one status quo.

cbm@well.com | This is why conservatives mostly agree,

 | and radicals always argue." - Brian Eno

At 11:16 AM -0800 1/11/08, mzed wrote:
>It has also come up recently that this message to line:
>
>"0., 6.931024 15000"
>
>is the same as
>
>"0. 0 6.931024 15000"
>
>I'd ditch the comma entirely, and work with a simpler message.

-- 
Chris Muir           | "There are many futures and only one status quo.
cbm@well.com         |  This is why conservatives mostly agree,
http://www.xfade.com |  and radicals always argue." - Brian Eno


Problems setting message