Re: [PD] hex loader
Hans-Christoph Steiner wrote: By the way, I just read thru the whole hexloader README. Looks like nice work, I think you covered every possibility that I could think of :) ah, finally someone who acknowledges my hard labour :-) fgmadsf rIOhannes ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] select issues
hi, I just found out, that [select] only throughputs floats and symbols, but not lists. [1 2 3 4 5( | [sel bla] will only output 1 on the right outlet, but not a the whole list. that is quite a limitation. but... ok. marius. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Beginners query: Calculating mouse speed
Hi, I have a really simple question: Does anyone know how to make a patch that will give me the speed the mouse is moving? I'm on windows and am using gemmouse to get the position. Thanks in advance! Rebecca. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Beginners query: Calculating mouse speed
Hi, One easy way would be to measure the number of pixels the mouse had moved since the previous frame. I attached an example that spits out 20 values per second, each number is the number of pixels the cursor has travelled since the previous frame. This patch only measures in the horizontal direction for simplicity. To also put the vertical axis in consideration, you will have to get the square root of (X^2 + Y^2) Also if the numbers change too rapidly for your needs, you will have to add some function to smooth the value changes. I hope this is of some help. -- David Shimamoto Hi, I have a really simple question: Does anyone know how to make a patch that will give me the speed the mouse is moving? I'm on windows and am using gemmouse to get the position. Thanks in advance! Rebecca. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list mouse_speed.pd Description: application/puredata ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] About editing pdpedia
On Nov 29, 2007, at 12:24 AM, PSPunch wrote: Hans, The lists are built automatically by mediawiki from every page that has [[Category:objectclass]] and [[Category:vanilla]] in it. In this case, 'Category' and 'Object class' is replaced by the localized term defined in the template.. I see the links in the Spanish page functioning properly in this manner. Combinations I've tried so far do not seem to work. Am I the only one dealing with multi byte characters at this site so far? I am beginning to have a bad feeling about their behavior. Yeah, you are the first working with multi-byte characters. The Chinese and Japanese wikipedia sites are pretty large, so I think that multi-byte characters should work fine. I don't think any of us are experts in MediaWiki, the software used for Pdpedia. You might try a mediawiki forum. .hc -- David Shimamoto .hc On Nov 28, 2007, at 12:12 PM, PSPunch wrote: Hans, Ok, I figure only the page names are copied. One last question if before I start adding text.. I don't quite understand the mechanism behind pages such as, http://wiki.puredata.info/en/Category:objectclass http://wiki.puredata.info/en/Category:vanilla Can you please tell me where the list of objects come from? -- David Shimamoto Looks like you got the Infobox working now. As for the English content, none of the previous people wanted to have the English content in their template import, so I didn't include it. It's all available by clicking the English link on the lower left of each page. .hc On Nov 28, 2007, at 3:15 AM, PSPunch wrote: Hans, Thanks. I am terribly sorry to bother you with this. To my eyes, the following two pages look almost identical. http://wiki.puredata.info/en/MediaWiki:Common.css http://wiki.puredata.info/ja/MediaWiki:Common.css http://wiki.puredata.info/en/Template:Infobox_Objectclass http://wiki.puredata.info/ja/Template:Infobox_Objectclass --- After you've kindly executed the import, I was imagining that for example, http://wiki.puredata.info/ja/line would be filled with English contents identical to http://wiki.puredata.info/ja/line Unless I've done something wrong, I am imagining I've translated terms I shouldn't have in the original template. Say, for example, is 'Category:' parsed exceptionally for specific actions? Then it shouldn't have been replaced with multi byte characters of my language. Any ideas? -- David Shimamoto On Nov 27, 2007, at 12:03 AM, PSPunch wrote: Hans, Ok, it's running, it'll take an hour or two. You can see the pages as they are imported: http://wiki.puredata.info/ja/minimum Thanks for the effort! Yes, I see the log increasing as a reload the recent changes page. Is it just me or is it general to get excited watching massive data being crunched right in front of your very eyes? Some pages I opened were just blank. I wonder if this is because the original English page is also blank... any way I will wait for the processing to end. There shouldn't be blank pages, but they will just be templates with the infobox and the categories setup. Next, you need to add the CSS and Infobox template then the infobox stuff will show up. I feel I've already done this following the admin HOW-TO. If it gets over written, I guess I can just try again. I think it's still missing the CSS, that should be listed on the HOWTO. That's why the Infobox isn't showing up. .hc doh itashimashite (that's one of my favorite words in japanese :D ) Yes, domo-arigato-gozaimas!! .hc On Nov 24, 2007, at 8:30 PM, PSPunch wrote: Hans, Most of the main page is taken from the documents kindly prepared by Tetsuya Saito. The objectclass template page mainly has terms unified with the main page. So for that part I feel comfortable to proceed. I'd appreciate it if you can execute the import. Thanks. :) -- David Shimamoto I can execute the import whenever you're ready. Maybe it would be good to have one more Japanese speaker look at the template? It's up to you. .hc On Nov 19, 2007, at 9:57 PM, PSPunch wrote: Hans, Thanks. I've followed the procedure in the English 'Admin howtos' pages. I would appreciate it if you could try executing the import. Thanks. -- David Shimamoto Hans-Christoph Steiner wrote On Nov 19, 2007, at 2:20 AM, PSPunch wrote: Hi list, I have some questions for some of you working on pdpedia. === 1. Has there already been discussions on policies regarding when/which pages to lock? I am assuming that leaving everything unlocked is the way to go if only the world were an ideal place. Are there not yet MediaWiki spammers? Locking pages is basically for when people are fighting over a page. I can't imagine that anything is so divisive in Pd that we'd need to lock pages. So far, we haven't had any spam yet.
Re: [PD] Beginners query: Calculating mouse speed
[MouseState] in cyclone gives you something like speed (change in postion) in addition to pixel positions. .hc On Nov 29, 2007, at 4:40 AM, Rebecca Schatz wrote: Hi, I have a really simple question: Does anyone know how to make a patch that will give me the speed the mouse is moving? I'm on windows and am using gemmouse to get the position. Thanks in advance! Rebecca. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list I spent 33 years and four months in active military service and during that period I spent most of my time as a high class muscle man for Big Business, for Wall Street and the bankers. - General Smedley Butler ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
Hmm, I suppose it should pass thru every thing unmodified on the right outlet. Can anyone think of any problems or disadvantages of [select] just outputting the unmatched input intact on the right outlet? .hc On Nov 29, 2007, at 3:12 AM, marius schebella wrote: hi, I just found out, that [select] only throughputs floats and symbols, but not lists. [1 2 3 4 5( | [sel bla] will only output 1 on the right outlet, but not a the whole list. that is quite a limitation. but... ok. marius. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list 'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2, by Mohja Kahf ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
On Thu, 2007-11-29 at 10:46 -0500, Hans-Christoph Steiner wrote: Hmm, I suppose it should pass thru every thing unmodified on the right outlet. Can anyone think of any problems or disadvantages of [select] just outputting the unmatched input intact on the right outlet? yeah, please don't change its behaviour only in pd-extended, so that patches created in pd-extended can cause errors in pd-vanilla. if changed, it needs to be changed in both. roman ___ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
I think [select] always worked that way since the beginning of Pd. it is also the case in max. I don't know if it is a good idea to change the behaviour, since it is easy to find a work around and might brake patches. but personally, of course I would like to see the change, at least it needs to be documented. it probably was documented in the original helpfile, but it is not documented in the pddp help patch. is there a workflow for changes in helppatches. how do I submit changes. and a wish related to that topic: please keep/make helpfiles read/writeable! marius. Hans-Christoph Steiner wrote: Hmm, I suppose it should pass thru every thing unmodified on the right outlet. Can anyone think of any problems or disadvantages of [select] just outputting the unmatched input intact on the right outlet? .hc On Nov 29, 2007, at 3:12 AM, marius schebella wrote: hi, I just found out, that [select] only throughputs floats and symbols, but not lists. [1 2 3 4 5( | [sel bla] will only output 1 on the right outlet, but not a the whole list. that is quite a limitation. but... ok. marius. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list 'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2, by Mohja Kahf ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
On Nov 29, 2007, at 12:46 PM, marius schebella wrote: I think [select] always worked that way since the beginning of Pd. it is also the case in max. I don't know if it is a good idea to change the behaviour, since it is easy to find a work around and might brake patches. If someone is relying on [select] to trim lists, that would be either unintentional, or some odd programming, IMHO. I think it's worth it. There have been more severe changes in the past, like atan switching inlets, there could be a warning like warning passing data thru unchanged, this is new behavior in 0.41. but personally, of course I would like to see the change, at least it needs to be documented. it probably was documented in the original helpfile, but it is not documented in the pddp help patch. Please add it to PDDP help patch and submit it to the tracker. Then I can check it in. is there a workflow for changes in helppatches. how do I submit changes. and a wish related to that topic: please keep/make helpfiles read/ writeable! chmod -R +w /Applications/Pd-extended.app/Contents/Resources/doc/ .hc marius. Hans-Christoph Steiner wrote: Hmm, I suppose it should pass thru every thing unmodified on the right outlet. Can anyone think of any problems or disadvantages of [select] just outputting the unmatched input intact on the right outlet? .hc On Nov 29, 2007, at 3:12 AM, marius schebella wrote: hi, I just found out, that [select] only throughputs floats and symbols, but not lists. [1 2 3 4 5( | [sel bla] will only output 1 on the right outlet, but not a the whole list. that is quite a limitation. but... ok. marius. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list - --- 'You people have such restrictive dress for women,’ she said, hobbling away in three inch heels and panty hose to finish out another pink-collar temp pool day. - “Hijab Scene #2, by Mohja Kahf Computer science is no more related to the computer than astronomy is related to the telescope. -Edsger Dykstra ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
On Thu, 2007-11-29 at 03:12 -0500, marius schebella wrote: hi, I just found out, that [select] only throughputs floats and symbols, but not lists. [1 2 3 4 5( | [sel bla] will only output 1 on the right outlet, but not a the whole list. that is quite a limitation. but... ok. marius. hm. i'd rather say, that the error messages it outputs are inconsistent. the help-file says, that it accepts numbers and symbols. i'd expect it to output an error, whenever a non-symbol or non-number message is received. however, what it does, is quite 'funny', if not to say 'frivolous': sending messages and corresponding error messages: [select three] 'list one 2'error: inlet: no method for 'float' 'list one two' no error 'symbol one'no error '3' no error 'one' error: select: no method for 'one' 'bang' error: select: no method for 'bang [select 3] 'list one 2'no error 'list one two' error: inlet: no method for 'symbol' 'symbol one'no error '3' no error 'one' error: select: no method for 'one' 'bang' error: select: no method for 'bang we see, that a [select symbol] outputs an error, if the second element of a list is a floar, and vice versa, a [select float] gives an error, if the second element of the incoming list is a symbol. i think, there is no explanation, that would make this behaviour to seem logical. use [route] for message with n!=1 elements. i'd expect [select] to work with only n=1 element lists and everything at least looks to be consistent. roman ___ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
On Thu, 2007-11-29 at 12:56 -0500, Hans-Christoph Steiner wrote: On Nov 29, 2007, at 12:36 PM, Roman Haefeli wrote: On Thu, 2007-11-29 at 10:46 -0500, Hans-Christoph Steiner wrote: Hmm, I suppose it should pass thru every thing unmodified on the right outlet. Can anyone think of any problems or disadvantages of [select] just outputting the unmatched input intact on the right outlet? yeah, please don't change its behaviour only in pd-extended, so that patches created in pd-extended can cause errors in pd-vanilla. if changed, it needs to be changed in both. Anything I change I submit to the patch tracker, so it's up to Miller then. oh, good to know ;-) roman ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
What is [select] supposed to do with a list? Just select based on the first element? I think it should reject lists altogether and suggest the use of [route]. Martin ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
Martin Peach wrote: What is [select] supposed to do with a list? Just select based on the first element? I think it should reject lists altogether and suggest the use of [route]. I think yes, reject it or output it untouched at the right inlet. m. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
Hallo, Roman Haefeli hat gesagt: // Roman Haefeli wrote: On Thu, 2007-11-29 at 12:56 -0500, Hans-Christoph Steiner wrote: On Nov 29, 2007, at 12:36 PM, Roman Haefeli wrote: yeah, please don't change its behaviour only in pd-extended, so that patches created in pd-extended can cause errors in pd-vanilla. if changed, it needs to be changed in both. Anything I change I submit to the patch tracker, so it's up to Miller then. oh, good to know ;-) Though as long as Miller doesn't accept the patch, you have incompatibilities on the language level. Ciao -- Frank Barknecht _ __footils.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: Hmm, I suppose it should pass thru every thing unmodified on the right outlet. Can anyone think of any problems or disadvantages of [select] just outputting the unmatched input intact on the right outlet? Yes, I can! [select] like many objects distributes incoming messages over its inlets, so passing lists unchanged to the right outlet may let all hell break loose with old patches. Example: [5 5( | | [select] | | | [print MISS] | [print HIT] will *always* print HIT because the second 5 in the list will first set the value, that [select] selects, the left 5 then will trigger a hit. A message 1 2 however will always pass the 1 to the MISS outlet, after the 2 in the list has set the select-target. Ciao -- Frank Barknecht _ __footils.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
Hallo, Roman Haefeli hat gesagt: // Roman Haefeli wrote: hm. i'd rather say, that the error messages it outputs are inconsistent. the help-file says, that it accepts numbers and symbols. i'd expect it to output an error, whenever a non-symbol or non-number message is received. however, what it does, is quite 'funny', if not to say 'frivolous': sending messages and corresponding error messages: [select three] 'list one 2' error: inlet: no method for 'float' 'list one two'no error 'symbol one' no error '3' no error 'one' error: select: no method for 'one' 'bang'error: select: no method for 'bang [select 3] 'list one 2' no error 'list one two'error: inlet: no method for 'symbol' 'symbol one' no error '3' no error 'one' error: select: no method for 'one' 'bang'error: select: no method for 'bang [select] distributes lists over its inlets, so this behaviour looks correct. See my other mail. Ciao -- Frank Barknecht _ __footils.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
On Thu, 2007-11-29 at 22:37 +0100, Frank Barknecht wrote: Hallo, Roman Haefeli hat gesagt: // Roman Haefeli wrote: hm. i'd rather say, that the error messages it outputs are inconsistent. the help-file says, that it accepts numbers and symbols. i'd expect it to output an error, whenever a non-symbol or non-number message is received. however, what it does, is quite 'funny', if not to say 'frivolous': sending messages and corresponding error messages: [select three] 'list one 2'error: inlet: no method for 'float' 'list one two' no error 'symbol one'no error '3' no error 'one' error: select: no method for 'one' 'bang' error: select: no method for 'bang [select 3] 'list one 2'no error 'list one two' error: inlet: no method for 'symbol' 'symbol one'no error '3' no error 'one' error: select: no method for 'one' 'bang' error: select: no method for 'bang [select] distributes lists over its inlets, so this behaviour looks correct. See my other mail. thanks for clarification. once again i just forgot about this distribution behaviour. makes perfectly sense to me now. everything is in order and consistent ah... nicee.. ;-) roman ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
got it. but it does not explain, the following: [select 1 2 3] has only one input. so no need to distribute anything. then send the message [4 4 4 4( no bang on the first outlet, but on the last one, but why is still only the first element on the list passed? just want to point out, that select just does not work for messages. marius. Frank Barknecht wrote: Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: Hmm, I suppose it should pass thru every thing unmodified on the right outlet. Can anyone think of any problems or disadvantages of [select] just outputting the unmatched input intact on the right outlet? Yes, I can! [select] like many objects distributes incoming messages over its inlets, so passing lists unchanged to the right outlet may let all hell break loose with old patches. Example: [5 5( | | [select] | | | [print MISS] | [print HIT] will *always* print HIT because the second 5 in the list will first set the value, that [select] selects, the left 5 then will trigger a hit. A message 1 2 however will always pass the 1 to the MISS outlet, after the 2 in the list has set the select-target. Ciao ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] non-selectable data structure
Dear all Can someone tell me please if there is any way to keep a structure (in a data structure patch) non-selectable? There is any flag who makes this. Could someone give me also an example please. Thanks in advance. All the best, Gilberto _ Transfira JÁ a última versão do Windows Live Messenger! http://get.live.com/pt-pt/messenger/overview ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
On Thu, Nov 29, 2007 at 10:27:07PM +0100, Frank Barknecht wrote: Roman Haefeli hat gesagt: // Roman Haefeli wrote: On Thu, 2007-11-29 at 12:56 -0500, Hans-Christoph Steiner wrote: On Nov 29, 2007, at 12:36 PM, Roman Haefeli wrote: yeah, please don't change its behaviour only in pd-extended, so that patches created in pd-extended can cause errors in pd-vanilla. if changed, it needs to be changed in both. Anything I change I submit to the patch tracker, so it's up to Miller then. oh, good to know ;-) Though as long as Miller doesn't accept the patch, you have incompatibilities on the language level. Which has bitten me on the ass at least once when making music with someone who uses pd-extended. Hans, I wonder if you could make it clear to people who download pd-extended that it is incompatible with Pd, an older version, and that it is bundled with many externals which aren't in Pd by default? Note that I really appreciate all the work you are doing to make people's lives easier, and don't want to put a dent in your efforts. I just think if we're not careful with breaking compatability people are going to get very confused very quickly. Best, Chris. --- http://mccormick.cx ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] non-selectable data structure
On Nov 30, 2007 2:25 AM, gilberto bernardes [EMAIL PROTECTED] wrote: Dear all Can someone tell me please if there is any way to keep a structure (in a data structure patch) non-selectable? An -x at the beginning of [drawpolygon] will make it so. The help patch for [drawpolygon] mentions it, but I don't see an example. I could whip one up later. -Chuckk -- http://www.badmuthahubbard.com ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] select issues
On Nov 29, 2007 8:45 PM, Martin Peach [EMAIL PROTECTED] wrote: What is [select] supposed to do with a list? Just select based on the first element? I think it should reject lists altogether and suggest the use of [route]. I agree with Martin. [route] is meant for lists, [select] is meant for floats or symbols. I suppose lists don't work with [select] for the same reason [route] doesn't have a right inlet, considering what Frank pointed out. If you connect all but the right outlet of [route] to [b], you have a [select] that handles lists and has no right inlet. -Chuckk -- http://www.badmuthahubbard.com ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
