hey ben,
...bringing this back:
On Oct 20, 2005, at 6:23 AM, B. Bogart wrote:
Indeed it seems entry is broken on .39, I'm still using .38
Anyone feel free to take a look and see whats up, as I'll probably not have time to look at it any time soon. I guess something in gcanvas is not working as in 38...
...grrr, turns out I can't get it to behave with pd-extended-RC5, which is 0.38-4...so any idea which pd it last worked on? When hitting bang, I get "unmatched open quote in list"...also, does this mean it just outputs the text as a list of symbols?
james
Hi Jamie,
I'm using the debian package for 0.38-4 and it works fine.
It sounds like your sending a message not possible in PD, could you send me an example snip that is causing the issue?
Everything typed into [entry] must be valid as what is typed in a messagebox. here are a few examples: -> means results in
hello -> symbol hello whats up -> list whats up 10 -> 10 0.0000001 -> 1e-07 "hello" -> symbol "hello" " hello " -> list " hello " ; test hello -> send [r test] hello {hello} -> symbol {hello} \n -> symbol n
since there is no string type this seemed the most logical way to do things
I've also used it with [tosymbol] but I don't have that external on this machine here...
I fear the text you are entering may have symbols giving PD, and therefore entry, trouble. :(
b.
hey ben,
...bringing this back:
On Oct 20, 2005, at 6:23 AM, B. Bogart wrote:
Indeed it seems entry is broken on .39, I'm still using .38
Anyone feel free to take a look and see whats up, as I'll probably not have time to look at it any time soon. I guess something in gcanvas is not working as in 38...
...grrr, turns out I can't get it to behave with pd-extended-RC5, which is 0.38-4...so any idea which pd it last worked on? When hitting bang, I get "unmatched open quote in list"...also, does this mean it just outputs the text as a list of symbols?
james
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
On Dec 2, 2005, at 10:41 AM, B. Bogart wrote
I'm using the debian package for 0.38-4 and it works fine.
...I'm using the pd-extended RC5, which is 0.38-4, but also I've tried on 0.39-1 in pd++.app...
It sounds like your sending a message not possible in PD, could you send me an example snip that is causing the issue?
...hmm: all I'm doing is opening help-entry.pd, clicking on one of the messages, then banging the entry box, with the expectation that something will be printed to console, but it never does...as a matter of fact, I have no idea what the example/help patch outputs are supposed to do, since they don't seem to do anything no matter what message I input in the help patch...
Everything typed into [entry] must be valid as what is typed in a messagebox. here are a few examples: -> means results in
hello -> symbol hello whats up -> list whats up 10 -> 10 0.0000001 -> 1e-07 "hello" -> symbol "hello" " hello " -> list " hello " ; test hello -> send [r test] hello {hello} -> symbol {hello} \n -> symbol n
since there is no string type this seemed the most logical way to do things
I've also used it with [tosymbol] but I don't have that external on this machine here...
I fear the text you are entering may have symbols giving PD, and therefore entry, trouble. :(
...I fear it's just an osx thing, so I'm looking for other solutions...
james
Hmmm
I know it does not work in 0.39, but in 0.38 it should be fine. I use it on OSX as well!!
so try this:
[set hello, bang< | [entry] | [print]
you should see "symbol hello" in the console.
Do you??
b.
On Dec 2, 2005, at 10:41 AM, B. Bogart wrote
I'm using the debian package for 0.38-4 and it works fine.
...I'm using the pd-extended RC5, which is 0.38-4, but also I've tried on 0.39-1 in pd++.app...
It sounds like your sending a message not possible in PD, could you sendhttp://www.axis.chttp://www.axis.com/products/cam_207/om/products/cam_207/ me an example snip that is causing the issue?
...hmm: all I'm doing is opening help-entry.pd, clicking on one of the messages, then banging the entry box, with the expectation that something will be printed to console, but it never does...as a matter of fact, I have no idea what the example/help patch outputs are supposed to do, since they don't seem to do anything no matter what message I input in the help patch...
Everything typed into [entry] must be valid as what is typed in a messagebox. here are a few examples: -> means results in
hello -> symbol hello whats up -> list whats up 10 -> 10 0.0000001 -> 1e-07 "hello" -> symbol "hello" " hello " -> list " hello " ; test hello -> send [r test] hello {hello} -> symbol {hello} \n -> symbol n
since there is no string type this seemed the most logical way to do things
I've also used it with [tosymbol] but I don't have that external on this machine here...
I fear the text you are entering may have symbols giving PD, and therefore entry, trouble. :(
...I fear it's just an osx thing, so I'm looking for other solutions...
james
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
On Dec 2, 2005, at 3:05 PM, B. Bogart wrote:
Hmmm
I know it does not work in 0.39, but in 0.38 it should be fine. I use it on OSX as well!!
so try this:
[set hello, bang< | [entry] | [print]
you should see "symbol hello" in the console.
Do you??
...nope: I get the following in the puredata console:
tried /Users/tigital/Desktop/PureData.app/Contents/Resources/ Scripts/../extra/entry.pd_darwin and succeeded Text v0.1 Ben Bogart. CVS: $Revision: 1.4 $ $Date: 2005/08/23 12:24:16 $ entry: You must enter at least 4 arguments. Default values used.
...and in the system console log (I guess you don't use post() but instead use printf()?):
unmatched open quote in list
l8r, james
james tittle wrote:
CVS: $Revision: 1.4 $ $Date: 2005/08/23 12:24:16 $ entry: You must enter at least 4 arguments. Default values used.
...and in the system console log (I guess you don't use post() but instead use printf()?):
unmatched open quote in list
i guess, tcl/tk is throwing that error. and there might be a missing closing quote in the strings for communication between pd & tcl/tk
mfg.ad.sr IOhannes
On Fri, 2 Dec 2005, IOhannes m zmölnig wrote:
james tittle wrote:
CVS: $Revision: 1.4 $ $Date: 2005/08/23 12:24:16 $ entry: You must enter at least 4 arguments. Default values used. ...and in the system console log (I guess you don't use post() but instead use printf()?): unmatched open quote in list
i guess, tcl/tk is throwing that error. and there might be a missing closing quote in the strings for communication between pd & tcl/tk
Btw DesireData has that bug fixed since yesterday. I posted a short snippet to pd-dev which may help those who want to patch their own pd too.
____________________________________________________________________ Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada
Hi James and Hans,
Seems that the version of [entry] included in the RC4 and RC5 installers is broken on OSX. I wanted to send this email before looking into it further. The fix is to use the entry I compiled for OSX included in pixelTANGO.
Just replace the RC4/5 entry with the pixelTANGO entry.pd_darwin and you should be in shape.
I'll try and figure out why hans's build is created a broken binary somehow..? My entry was just compiled from CVS!!
I'll look into this as soon as I can.
Thanks for noticing Jamie!
b.
james tittle wrote:
hey ben,
...bringing this back:
On Oct 20, 2005, at 6:23 AM, B. Bogart wrote:
Indeed it seems entry is broken on .39, I'm still using .38
Anyone feel free to take a look and see whats up, as I'll probably not have time to look at it any time soon. I guess something in gcanvas is not working as in 38...
...grrr, turns out I can't get it to behave with pd-extended-RC5, which is 0.38-4...so any idea which pd it last worked on? When hitting bang, I get "unmatched open quote in list"...also, does this mean it just outputs the text as a list of symbols?
james
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I assume by not working, you mean that it doesn't output text. But everything else about it seems to work fine.
How did you compile [entry]? The only difference that I can see between externals/bbogart/entry/makefile and externals/build/darwin/makefile is this:
externals/build/darwin/makefile: LDFLAGS = -bundle -bundle_loader $(PDEXECUTABLE) -L/sw/lib
externals/bbogart/entry/makefile cc -bundle -undefined suppress -flat_namespace -o $*.pd_darwin $*.o
The compiled size is much different:
hans@sla:entry > ls -l entry.pd_darwin - -rw-r--r-- 1 hans staff 14268 Dec 3 13:09 entry.pd_darwin hans@sla:entry > ls -l /Applications/Pd-0.38.4-extended-RC5.app/Contents/Resources/extra/ entry.pd_darwin - -rwxr-xr-x 1 hans admin 34960 Nov 27 00:09 /Applications/Pd-0.38.4-extended-RC5.app/Contents/Resources/extra/ entry.pd_darwin*
I tried the directly compiled version (i.e. the smaller one) and it behaves the same, no text output).
What version of Tcl/Tk did you use for pixelTANGO? I am compiling against 8.4.9.
.hc
On Dec 3, 2005, at 11:56 AM, B. Bogart wrote:
Hi James and Hans,
Seems that the version of [entry] included in the RC4 and RC5 installers is broken on OSX. I wanted to send this email before looking into it further. The fix is to use the entry I compiled for OSX included in pixelTANGO.
Just replace the RC4/5 entry with the pixelTANGO entry.pd_darwin and you should be in shape.
I'll try and figure out why hans's build is created a broken binary somehow..? My entry was just compiled from CVS!!
I'll look into this as soon as I can.
Thanks for noticing Jamie!
b.
james tittle wrote:
hey ben,
...bringing this back:
On Oct 20, 2005, at 6:23 AM, B. Bogart wrote:
Indeed it seems entry is broken on .39, I'm still using .38
Anyone feel free to take a look and see whats up, as I'll probably not have time to look at it any time soon. I guess something in gcanvas is not working as in 38...
...grrr, turns out I can't get it to behave with pd-extended-RC5, which is 0.38-4...so any idea which pd it last worked on? When hitting bang, I get "unmatched open quote in list"...also, does this mean it just outputs the text as a list of symbols?
james
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
________________________________________________________________________ ____
"The arc of history bends towards justice." - Dr. Martin Luther King, Jr.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
By the way, the same thing happens with the Windows build, which is built against Tcl/Tk 8.4.11
.hc
On Dec 3, 2005, at 1:28 PM, Hans-Christoph Steiner wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I assume by not working, you mean that it doesn't output text. But everything else about it seems to work fine.
How did you compile [entry]? The only difference that I can see between externals/bbogart/entry/makefile and externals/build/darwin/makefile is this:
externals/build/darwin/makefile: LDFLAGS = -bundle -bundle_loader $(PDEXECUTABLE) -L/sw/lib
externals/bbogart/entry/makefile cc -bundle -undefined suppress -flat_namespace -o $*.pd_darwin $*.o
The compiled size is much different:
hans@sla:entry > ls -l entry.pd_darwin
- -rw-r--r-- 1 hans staff 14268 Dec 3 13:09
entry.pd_darwin hans@sla:entry > ls -l /Applications/Pd-0.38.4-extended-RC5.app/Contents/Resources/extra/ entry.pd_darwin
- -rwxr-xr-x 1 hans admin 34960 Nov 27 00:09
/Applications/Pd-0.38.4-extended-RC5.app/Contents/Resources/extra/ entry.pd_darwin*
I tried the directly compiled version (i.e. the smaller one) and it behaves the same, no text output).
What version of Tcl/Tk did you use for pixelTANGO? I am compiling against 8.4.9.
.hc
On Dec 3, 2005, at 11:56 AM, B. Bogart wrote:
Hi James and Hans,
Seems that the version of [entry] included in the RC4 and RC5 installers is broken on OSX. I wanted to send this email before looking into it further. The fix is to use the entry I compiled for OSX included in pixelTANGO.
Just replace the RC4/5 entry with the pixelTANGO entry.pd_darwin and you should be in shape.
I'll try and figure out why hans's build is created a broken binary somehow..? My entry was just compiled from CVS!!
I'll look into this as soon as I can.
Thanks for noticing Jamie!
b.
james tittle wrote:
hey ben,
...bringing this back:
On Oct 20, 2005, at 6:23 AM, B. Bogart wrote:
Indeed it seems entry is broken on .39, I'm still using .38
Anyone feel free to take a look and see whats up, as I'll probably not have time to look at it any time soon. I guess something in gcanvas is not working as in 38...
...grrr, turns out I can't get it to behave with pd-extended-RC5, which is 0.38-4...so any idea which pd it last worked on? When hitting bang, I get "unmatched open quote in list"...also, does this mean it just outputs the text as a list of symbols?
james
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
"The arc of history bends towards justice." - Dr. Martin Luther King,
Jr. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (Darwin)
iD8DBQFDkePGN4PEFRUrWIsRAlUoAKDZwn+qWpLSwMtRpIZiMz8mN2NKwQCg0I9Q CHum6WyPs6GZpk6d0+hfLq4= =Bqok -----END PGP SIGNATURE-----
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
________________________________________________________________________ ____
I'm not sure if this should stay on gem-dev or what...
Anyhow I've traced the issue and here is where the problem lies. My original code outputted the symbol like so:
sys_vgui("pd [concat entry%p output [.x%x.c.s%x get 0.0 end] \;]\n", x, x->x_glist, x);
Johannes made the valiant effort to escape "," and ";" so that are not seperated into descrete messages in PD. Basically meaning you can't type a message for the entry widget containing messages for it, and you can't send to a receive directly from the widget. I think this is ok, but I did not see much reason to change it. His change looks like this:
sys_vgui("pd [concat entry%p output [string map {"," "\\," ";" "\\;} [.x%x.c.s%x get 0.0 end]]" \;]\n", x, x->x_glist, x);
I tried removing the
"
at:
end]]"
thinking that may be the problem, but indeed I can't make this code work with PD complaining about unmatches quotes. Worse than that is that the code works fine on my 8.4 interpreter, just not in PD...
So Johannes, since you introduced the bug, care to fix it?
Also the good news is that my original "unfixed" code worked fine on PD 0.39, so the issue was only Johannes's changes. Which also explains why popup works on 0.39, since it uses the same code to output.
Johannes, I really do appreciate your effort here, thanks for logging your changes also. Please do let me know when you make such future changes in an email though so I can make sure they work myself soon after you commit them.
Since you did write the extra code for escaping I'm sure your the best person to fix it.
Unless someone sees any reason why not I'll change the code back to the way it used to be and re-commit. I fear how many distros are running out there with broken [entry]s. :( Looks like it was commited in August.
Johannes, does this code really work on your machine?!?!! It certainly does not work on my linux machine, and the mac, and Han's reported it also not working on windows.
Johannes please reply to this email if you would not like me to recommit back to the code before your changes! (and provide a reason why) just to make sure you have the revision somewhere on your machine, though I guess you can get it from CVS. (revision 1.4 would be yours)
Thanks all for reporting this!
b.
Hans-Christoph Steiner wrote:
By the way, the same thing happens with the Windows build, which is built against Tcl/Tk 8.4.11
.hc
On Dec 3, 2005, at 1:28 PM, Hans-Christoph Steiner wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I assume by not working, you mean that it doesn't output text. But everything else about it seems to work fine.
How did you compile [entry]? The only difference that I can see between externals/bbogart/entry/makefile and externals/build/darwin/makefile is this:
externals/build/darwin/makefile: LDFLAGS = -bundle -bundle_loader $(PDEXECUTABLE) -L/sw/lib
externals/bbogart/entry/makefile cc -bundle -undefined suppress -flat_namespace -o $*.pd_darwin $*.o
The compiled size is much different:
hans@sla:entry > ls -l entry.pd_darwin
- -rw-r--r-- 1 hans staff 14268 Dec 3 13:09
entry.pd_darwin hans@sla:entry > ls -l /Applications/Pd-0.38.4-extended-RC5.app/Contents/Resources/extra/ entry.pd_darwin
- -rwxr-xr-x 1 hans admin 34960 Nov 27 00:09
/Applications/Pd-0.38.4-extended-RC5.app/Contents/Resources/extra/ entry.pd_darwin*
I tried the directly compiled version (i.e. the smaller one) and it behaves the same, no text output).
What version of Tcl/Tk did you use for pixelTANGO? I am compiling against 8.4.9.
.hc
On Dec 3, 2005, at 11:56 AM, B. Bogart wrote:
Hi James and Hans,
Seems that the version of [entry] included in the RC4 and RC5 installers is broken on OSX. I wanted to send this email before looking into it further. The fix is to use the entry I compiled for OSX included in pixelTANGO.
Just replace the RC4/5 entry with the pixelTANGO entry.pd_darwin and you should be in shape.
I'll try and figure out why hans's build is created a broken binary somehow..? My entry was just compiled from CVS!!
I'll look into this as soon as I can.
Thanks for noticing Jamie!
b.
james tittle wrote:
hey ben,
...bringing this back:
On Oct 20, 2005, at 6:23 AM, B. Bogart wrote:
Indeed it seems entry is broken on .39, I'm still using .38
Anyone feel free to take a look and see whats up, as I'll probably not have time to look at it any time soon. I guess something in gcanvas is not working as in 38...
...grrr, turns out I can't get it to behave with pd-extended-RC5, which is 0.38-4...so any idea which pd it last worked on? When hitting bang, I get "unmatched open quote in list"...also, does this mean it just outputs the text as a list of symbols?
james
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
"The arc of history bends towards justice." - Dr. Martin Luther King, Jr.