I've been complaining that we should be able to use "$0" in messages for the sake of simplicity. Apparently you can if you use "" before it... BUT... Pd does not allow you to write it... as if it REALLY did not want you to do it...
there are many things wrong with the backslash. if i put 92 through [makefilename %c] it makes two backslashes. if I use it as a $1 inside of a symbol it becomes four backslashes. if I try to print it, it becomes 8 backslashes (unless GridFlow is loaded, because it installs its own [print]).
Those hacks probably all come from trying to fix a backslash bug by brute force. By fixing the bug in three places, you cancel one of the original bugs by three new bugs opposite to the original one, so, whether that original bug shows up, you can get up to three new bugs stacked on each other, and then, most of the original bugs are still there (iemgui labels still can't take backslashes, etc).
That's just the backslashes... Keycode 123 is actually much more dangerous.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
so, is it a random bug? I thought it was on purpose... because of the no "$0" on messages philosophy...
more on that, if you type $0 in a sumbol box, the backlash appears there... if the message is sent through this symbol box, the $0 can actually function as it should on messages...
cheers
2010/4/17 Mathieu Bouchard matju@artengine.ca
I've been complaining that we should be able to use "$0" in messages for
the sake of simplicity. Apparently you can if you use "" before it... BUT... Pd does not allow you to write it... as if it REALLY did not want you to do it...
there are many things wrong with the backslash. if i put 92 through [makefilename %c] it makes two backslashes. if I use it as a $1 inside of a symbol it becomes four backslashes. if I try to print it, it becomes 8 backslashes (unless GridFlow is loaded, because it installs its own [print]).
Those hacks probably all come from trying to fix a backslash bug by brute force. By fixing the bug in three places, you cancel one of the original bugs by three new bugs opposite to the original one, so, whether that original bug shows up, you can get up to three new bugs stacked on each other, and then, most of the original bugs are still there (iemgui labels still can't take backslashes, etc).
That's just the backslashes... Keycode 123 is actually much more dangerous.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On Sat, 17 Apr 2010, Alexandre Porres wrote:
so, is it a random bug?
What's a "random bug" ?
I thought it was on purpose... because of the no "$0" on messages philosophy...
There's no philosophy behind that !
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
What's a "random bug" ?
"not on purpose"
2010/4/17 Mathieu Bouchard matju@artengine.ca
On Sat, 17 Apr 2010, Alexandre Porres wrote:
so, is it a random bug?
What's a "random bug" ?
I thought it was on purpose... because of the no "$0" on messages
philosophy...
There's no philosophy behind that !
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
if i put 92 through [makefilename %c]
oh, 44 gives back wierd stuff too "\,"
2010/4/17 Mathieu Bouchard matju@artengine.ca
I've been complaining that we should be able to use "$0" in messages for
the sake of simplicity. Apparently you can if you use "" before it... BUT... Pd does not allow you to write it... as if it REALLY did not want you to do it...
there are many things wrong with the backslash. if i put 92 through [makefilename %c] it makes two backslashes. if I use it as a $1 inside of a symbol it becomes four backslashes. if I try to print it, it becomes 8 backslashes (unless GridFlow is loaded, because it installs its own [print]).
Those hacks probably all come from trying to fix a backslash bug by brute force. By fixing the bug in three places, you cancel one of the original bugs by three new bugs opposite to the original one, so, whether that original bug shows up, you can get up to three new bugs stacked on each other, and then, most of the original bugs are still there (iemgui labels still can't take backslashes, etc).
That's just the backslashes... Keycode 123 is actually much more dangerous.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On Sat, 17 Apr 2010, Alexandre Porres wrote:
if i put 92 through [makefilename %c]
oh, 44 gives back wierd stuff too "\,"
44 59 92 123 125.
comma prints fine with GridFlow's [print], double-backslashed with Pd's [print].
semicolon prints single-backslashed with GridFlow's [print], triple-backslashed with Pd's [print].
Symbolbox (Ctrl+4) shows them the same way GridFlow's [print] does.
123 still crashes the Pd GUI... unless at the same time you try 125 immediately after that, using a [t] and/or a [delay]. (because you can't click anymore)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
-
Alexandre Porres -
Mathieu Bouchard