Menu ▾ ▴

#635 symbols containing spaces not exported correctly

v0.43
open
nobody
puredata (322)
5
2011-01-17
2010-12-04
Roman Haefeli
No

I just noticed, that one now can type spaces into a symbol box. This is great!!

In some cases such symbols break and are not interpreted as symbols any more due to the lack of the escaping character.

case 1):
send [symbolatom\ - [label $1( to a iemgui object and make sure, that you type a space. Save the patch and open it again. The properties of the iemgui cannot be displayed any more.

case 2):
send [symbolatom\ -> [send $1( to a [netsend] and make sure to type at least one 'space'. The [netreceive] on the other side will receive it as a message with more than one elements

Both cases could be fixed, if the symbol box would automatically pre-pend each ' ' with a '\'.

Discussion

  • IOhannes m zmölnig

    IOhannes m zmölnig - 2011-01-17

    hmm, but the bugs are clearly in [netsend] and iemguis, and not in symbolatom.
    why do you want to add a hack to symbolatom, rather than fix the problems in the other cases?

     

  • Roman Haefeli

    Roman Haefeli - 2011-01-17
    • summary: symbol-box does not escape 'space' characters with '\' --> symbols containing spaces not exported correctly
     

  • Roman Haefeli

    Roman Haefeli - 2011-01-17

    Yeah, only later I realised that as well. Symbols containing spaces are handled correctly as long as they remain inside Pd. As you state the problem is not a missing escape mechanism when creating symbols (as I erraneously assumed), but when exporting them. A few cases where symbols containing spaces fail:

    * [textfile]
    * label in the iemguis
    * FUDI
    * (probably more)

    Interestingly, [netreceive] will recognize symbols containing escaped spaces as such. So it seems the latter is half-way implemented.

    I changed the Summary.

     

Anonymous
Anonymous

Add attachments
Cancel