4s9kS2S09nTNbjnIMucgjhvX9zP5CLJ/IIvcTJrEo=; b=Vo4PWrnV6Uh5C4nsp3eMv6c+oL+RDjwfKXtWCFm0zDnKNMtYw1vcZszmKIy84X07nL 08/DyV48USPmm4cfw2WsFJXwATo6jxLxN0Ke2wqcfoT2ZzSFwFWKOfmR8zwU635wMAg2 Cjw5TpjDyul4uJ8tI3KQoN404QzAapS0vKduU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=i9o0IiH09p3BA0+KQwVrzOL/1Jq2RwSxuU5JQdZ2sZbWDmxO2lyFuNiIwekhxg3sY4 PukaPIOjpnZC2kcliDaz1x/hdT8ouuu9dG7U+F3mFsVplZ0EjKAqn/5tsb5LRxw2Qs4k HHEgOjjEvNSzzv5o/53VV2/MXJ1j++9kpDASw= MIME-Version: 1.0 Received: by 10.90.88.16 with SMTP id l16mr1724428agb.91.1247235810109; Fri, 10 Jul 2009 07:23:30 -0700 (PDT) In-Reply-To: 4A571357.8080603@iem.at References: 9693578e0907091706k278e17a6vb6780269e46e94f0@mail.gmail.com 4A571357.8080603@iem.at Date: Fri, 10 Jul 2009 11:23:30 -0300 Message-ID: 9693578e0907100723v5b409c56m5b6feae62439620b@mail.gmail.com From: glerm soares organismo@gmail.com To: IOhannes m zmoelnig zmoelnig@iem.at Content-Type: multipart/alternative; boundary=0016361648b369ab46046e5ab7bc X-Spam-Score: 0.0 X-Spam-Level: / X-Spam-Tests: AWL=0.046,HTML_MESSAGE=0.001 X-Spam-Score: 1.2 X-Spam-Level: + Cc: Pd List pd-list@iem.at Subject: Re: [PD] curly braces { } in pd ? X-BeenThere: pd-list@iem.at X-Mailman-Version: 2.1.11 Precedence: list List-Id: the PureData - mailinglist <pd-list.iem.at> List-Unsubscribe: http://lists.puredata.info/options/pd-list, mailto:pd-list-request@iem.at?subject=unsubscribe List-Archive: http://lists.puredata.info/pipermail/pd-list List-Post: mailto:pd-list@iem.at List-Help: mailto:pd-list-request@iem.at?subject=help List-Subscribe: http://lists.puredata.info/listinfo/pd-list, mailto:pd-list-request@iem.at?subject=subscribe X-List-Received-Date: Fri, 10 Jul 2009 14:22:42 -0000
--0016361648b369ab46046e5ab7bc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
I had checked the bug tracker before, but since was an old bug I was wondering if there was a way to solve.
i guess this is not quite true.
[bytes2any] should work just fine, only if you try to display the result in one or any way, the pd-gui will freeze.
to be precise, you are right. the pd freezes because the patch had a [ prepend set ] and then a message , to print the supposed conversion. Now I understood the issue.
Just for curiousity: Is there other characters where this happens?
I know another character bug(?) - I can't print "#" (hash character) in canvas (but it prints in messages and symbols)... In canvas # is changed for $ ...
thanx glerm
--0016361648b369ab46046e5ab7bc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
=A0I had checked the bug tracker before, but since was an old bug I was won= dering if there was a way to solve. <br> <br><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style= =3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; p= adding-left: 1ex;"> i guess this is not quite true.<br> [bytes2any] should work just fine, only if you try to display the result in= one or any way, the pd-gui will freeze.<br>
</blockquote><div><br>to be precise, you are right. the pd freezes because = the patch had a [ prepend set ]=A0 and then a message , to print the suppos= ed conversion. Now I understood the issue.<br><br>Just for curiousity: Is t= here other characters where this happens?<br> <br>I know another character bug(?) - I can't print "#" (hash= character) in canvas (but it prints in messages and symbols)... In canvas = # is changed for $ ...<br></div></div><br><br>thanx<br>glerm<br>
--0016361648b369ab46046e5ab7bc--