Hi,
I was checking out msgfile (zexy 2.1), and there are some inconsistencies
that I can't work out:
- the read message doesn't work with paths/files that have spaces in them
[that's not an inconsistency, but it's something that should be standard
nowadays]
- when opening the attached file with "|read ... cr(", msgfile behaves
differently in pd vanilla 0.40-2 and pd extended 0.39-2-t5 (the .dll file
only exists once, it's the one compiled with pd-extended). In pd extended
the file opens, but it disregards the "cr" command - and the attached file
appears condensed in 3 or 4 lines. In pd-vanilla the message "unable to
lseek" appears.
does someone gets the same results as I do?
Joao
On Wed, 2007-08-29 at 06:58 +0200, João Miguel Pais wrote:
Hi,
I was checking out msgfile (zexy 2.1), and there are some inconsistencies
that I can't work out:
- the read message doesn't work with paths/files that have spaces in them
[that's not an inconsistency, but it's something that should be standard
nowadays]
true, but i am not sure if it can be considered as a problem of [msgfile], but rather of pd in general, since there is no escape mechanism. i am even not sure, if it would be a good idea, that [msgfile] would accept lists, what you are actually requesting.
btw: afaik, you _can_ open files with a space in the path, but you need to create the symbol accordingly. for example, if you use [openpane] to get the path, it works, because [msgfile] gets a symbol containing spaces instead of a list in that case. alternatively you could also use [list2symbol] (which is also part of zexy) to create symbols with spaces, if you don't want to use [openpanel].
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
I also experienced many inconsistencies with msgfile. But I do not think it has to do with spaces. If you add data to a msgfile then send a "write /test" message, it answers "error: msgfile : failed to open /test"! When you try to read with "read /test" it answers "error: msgfile_read: unable to open test/test"!
Tom
On 8/29/07, João Miguel Pais jmmmpais@googlemail.com wrote:
Hi,
I was checking out msgfile (zexy 2.1), and there are some inconsistencies that I can't work out:
- the read message doesn't work with paths/files that have spaces in them
[that's not an inconsistency, but it's something that should be standard nowadays]
- when opening the attached file with "|read ... cr(", msgfile behaves
differently in pd vanilla 0.40-2 and pd extended 0.39-2-t5 (the .dll file only exists once, it's the one compiled with pd-extended). In pd extended the file opens, but it disregards the "cr" command - and the attached file appears condensed in 3 or 4 lines. In pd-vanilla the message "unable to lseek" appears.
does someone gets the same results as I do?
Joao
-- Friedenstr. 58 10249 Berlin Deutschland Tel +49 30 42020091 Mob +49 162 6843570 jmmmpais@googlemail.com skype: jmmmpjmmmp http://www.puredata.org/Members/jmmmp IBM Thinkpad R51, XP, Pd-Ext-0.39-2-t5 _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
hi.
Quoting Thomas O Fredericks tof@danslchamp.org:
I also experienced many inconsistencies with msgfile. But I do not think it has to do with spaces. If you add data to a msgfile then send a "write /test" message, it answers "error: msgfile : failed to open /test"!
this is not an inconsitency. you probaly do not have write-rights in / ??
When you try to read with "read /test" it answers "error: msgfile_read: unable to open test/test"!
this is not an inconsistency either.
msgfile uses pd's search-paths to search for the file. if pd cannot
find a file "test" it will also look for "test/test".
so if there was a file "/test" msgfile would just open it.
fmga.dsr IOhannes
This message was sent using IMP, the Internet Messaging Program.
this is not an inconsitency. you probaly do not have write-rights in / ??
Yeah, I actually figured it out after sending the message *my bad* But I did experience some weird stuff once. I will have to found out how to recreate the errors! But for now, I cannot. Sorry for the erroneous bug report!
Tom
On 8/30/07, zmoelnig@iem.at zmoelnig@iem.at wrote:
hi.
Quoting Thomas O Fredericks tof@danslchamp.org:
I also experienced many inconsistencies with msgfile. But I do not think
it
has to do with spaces. If you add data to a msgfile then send a "write /test" message, it answers "error: msgfile : failed to open /test"!
this is not an inconsitency. you probaly do not have write-rights in / ??
When you try to read with "read /test" it answers "error: msgfile_read: unable to open test/test"!
this is not an inconsistency either. msgfile uses pd's search-paths to search for the file. if pd cannot find a file "test" it will also look for "test/test". so if there was a file "/test" msgfile would just open it.
fmga.dsr IOhannes
This message was sent using IMP, the Internet Messaging Program.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Quoting João Miguel Pais jmmmpais@googlemail.com:
Hi,
I was checking out msgfile (zexy 2.1), and there are some inconsistencies that I can't work out:
- the read message doesn't work with paths/files that have spaces in
them [that's not an inconsistency, but it's something that should be standard nowadays]
i have not checked that now, but i am pretty sure, that it does
support files with spaces.
however, there is a limitation (that can be worked around) on pd's
ability to create a symbol containing spaces.
- when opening the attached file with "|read ... cr(", msgfile behaves
differently in pd vanilla 0.40-2 and pd extended 0.39-2-t5 (the .dll file only exists once, it's the one compiled with pd-extended). In pd extended the file opens, but it disregards the "cr" command - and the attached file appears condensed in 3 or 4 lines. In pd-vanilla the message "unable to lseek" appears.
are you absolutely sure that the same .dll is used? if so: weird...
mfg.adr IOhannes
does someone gets the same results as I do?
Joao
-- Friedenstr. 58 10249 Berlin Deutschland Tel +49 30 42020091 Mob +49 162 6843570 jmmmpais@googlemail.com skype: jmmmpjmmmp http://www.puredata.org/Members/jmmmp IBM Thinkpad R51, XP, Pd-Ext-0.39-2-t5
This message was sent using IMP, the Internet Messaging Program.
On Thu, 30 Aug 2007, zmoelnig@iem.at wrote:
i have not checked that now, but i am pretty sure, that it does support files with spaces. however, there is a limitation (that can be worked around) on pd's ability to create a symbol containing spaces.
It can also be fixed. If you edit the source code of pd, you only have to change two lines to fix the saving of spaces in symbols, but somehow so far it has been easier for everybody to write several hundred mails about the topic instead, and figuring out workarounds, teaching workshop students about not using spaces, and pondering whether it's a bug at all and how to think of it as a feature.
Pd might be Open-Source and all it implies, but for that particular case (and some other particular cases) it just feels like it's a regular freeware in which the author has lost the source code in a hard disk crash several years ago...
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
On Thu, 2007-08-30 at 12:29 -0400, Mathieu Bouchard wrote:
On Thu, 30 Aug 2007, zmoelnig@iem.at wrote:
i have not checked that now, but i am pretty sure, that it does support files with spaces. however, there is a limitation (that can be worked around) on pd's ability to create a symbol containing spaces.
It can also be fixed. If you edit the source code of pd, you only have to change two lines to fix the saving of spaces in symbols, but somehow so far it has been easier for everybody to write several hundred mails about the topic instead, and figuring out workarounds, teaching workshop students about not using spaces, and pondering whether it's a bug at all and how to think of it as a feature.
sometimes i label [cnv]'s and other gui objects with symbols containing spaces, often just because of cosmetic reasons. however, it needs a lot of work around it, because before saving the patch, you have to send 'label empty' first, otherwise the properties of the gui completely get screwed. and after loading the patch again, you need to set the label again, of course. i didn't know, that it would be such an easy fix in the source of pd. so many people are using pd everyday, that i believe, just this little fix would save a huge amount of man hours every year, so that it is _really_ worth it.
just my two cents.
roman
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Mathieu Bouchard wrote:
On Thu, 30 Aug 2007, zmoelnig@iem.at wrote:
i have not checked that now, but i am pretty sure, that it does support files with spaces. however, there is a limitation (that can be worked around) on pd's ability to create a symbol containing spaces.
It can also be fixed. If you edit the source code of pd, you only have to change two lines to fix the saving of spaces in symbols, but somehow so far it has been easier for everybody to write several hundred mails
fine. please submit a patch to the patch-tracker at sourceforge. (or send your 2 lines of code directly to me, if you prefer it that way)
mfa.dr IOhannes
Quoting João Miguel Pais jmmmpais@googlemail.com:
Hi,
I was checking out msgfile (zexy 2.1), and there are some
now that's an old version of zexy, btw...
mfga.dsr IOhannes
This message was sent using IMP, the Internet Messaging Program.
-
hard off -
IOhannes m zmoelnig -
João Miguel Pais -
Mathieu Bouchard -
Roman Haefeli -
Thomas O Fredericks -
zmoelnig＠iem.at