Hi!
I found that [print] limits the output of the second symbol in a list. Printing a very long symbol works fine, but if the long symbol comes behind a short one, [print] shows the first one and cuts the second one with a * at the end just like this:
[abcdef( | [print]
Works fine showing "abcdef" (abcdef is very long symbol, say 100 characters)
[a abcdef( | [print]
Results in "a abc*" !
See attached patch, as well.
Is this a feature, a bug, is it documented, why not cut the first symbol too? Just some questions...
br, Piotr
Quoting Piotr Majdak piotr@majdak.com:
Works fine showing "abcdef" (abcdef is very long symbol, say 100 characters)
[a abcdef( | [print]
Results in "a abc*" !
oh does it ? i think that's the 3rd time in the last week i am writing to pd-related lists (once to gem-dev, one to pd-list (or was it pd-dev ??) about this very behaviour of [print].
Is this a feature, a bug, is it documented, why not cut the first symbol
i think none of them (i guess it's a safety check against locking the connection between pd and pd-gui; so that would be a feature if you have stability in mind; for most others it might appear a bug)
why it is not working on the "first symbol" is probably, because it is considered a selector rather than a symbol. (don't know though; i would have to check the code - should be in s_print.c)
mfg.asd.r IOhannes
zmoelnig@iem.at wrote:
oh does it ? i think that's the 3rd time in the last week i am writing to pd-related lists (once to gem-dev, one to pd-list (or was it pd-dev ??) about this very behaviour of [print].
I found:
http://lists.puredata.info/pipermail/pd-list/2005-09/030947.html
"there is definitely i limit in [print]; there might be a limit in the symbol-length but i never found one (the longest symbol i ever made was some 20.000 chars long)"
The bug/feature I found concerns symbol lists, where the second symbol is cut if it exceeds appr. 100 characters. Thus, I didn't see any link to your comment about a limit of 20.000 chars and my bug report.
Is this a feature, a bug, is it documented, why not cut the first symbol
i think none of them (i guess it's a safety check against locking the connection between pd and pd-gui; so that would be a feature if you have stability in mind; for most others it might appear a bug)
OK. I think, this behaviour should be mentioned in print-help.pd. What is the right branch to check-in this kind of changes? (I've never contributed to pd CVS)
br, Piotr
PS: @Hannes: sorry being unsubscribed to gem-dev and pd-dev lists. I'm sure you contribute to any many other discussions which I neither read nor understand. I'm just a pd user and I know it - there's no need to remind me about that...
Quoting Piotr Majdak piotr@majdak.com:
"there is definitely i limit in [print]; there might be a limit in the symbol-length but i never found one (the
longest symbol i ever made was some 20.000 chars long)"
The bug/feature I found concerns symbol lists, where the second symbol
is cut if it exceeds appr. 100 characters. Thus, I didn't see any link
to your comment about a limit of 20.000 chars and my bug report.
actually we are talking about the same thing. the 20.000 characters which i tested have only been to illustrate that the symbol itself is not corrupted, just the [print]. and it has no answer to why the 1st "symbol" is not affected.
OK. I think, this behaviour should be mentioned in print-help.pd. What
is the right branch to check-in this kind of changes? (I've never contributed to pd CVS)
yes i agree that it should go into the documentation. however the policy is, that only miller has to rights to write to the main-trunk of pd in the CVS. so the best thing (i think) would be to submit a patch to the patch-tracker at the sourceforge site (assign it to miller if possible) miller goes them through now and then and accepts them or not.
PS: @Hannes: sorry being unsubscribed to gem-dev and pd-dev lists. I'm
http://lists.puredata.info/pipermail/pd-list/2005-09/030947.html
so it has been on the pd-list which i think you are subscribed to.
sure you contribute to any many other discussions which I neither read
of course it was stupid on my side to bring in other (totally unrelated) discussions. if i tell my girlfriend about the peculiarities of [print] is should not expect you (or anyone else) to know.
i am sorry for that.
nor understand. I'm just a pd user and I know it - there's no need to remind me about that...
i don't see how i would have "degraded" you to an ordinary pd-user (i consider myself one of this people)
mfg.asdr.er IOhannes
zmoelnig@iem.at wrote:
Quoting Piotr Majdak piotr@majdak.com:
yes i agree that it should go into the documentation. however the policy is, that only miller has to rights to write to the main-trunk of pd in the CVS. so the best thing (i think) would be to submit a patch to the patch-tracker at the sourceforge site (assign it to miller if possible) miller goes them through now and then and accepts them or not.
Thanks - I'll do that the way you propose.
br, Piotr
-
Piotr Majdak -
zmoelnig＠iem.at