According to the help patch, the argument of pow~ should initiate the right inlet, but it doesn't seem to work. (Please see the attached patch.)
Best, Peiman
*www.peimankhosravi.co.uk || RSS Feedhttp://peimankhosravi.co.uk/miscposts.rss || Concert News http://spectralkimia.wordpress.com/*
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-10-28 10:00, peiman khosravi wrote:
According to the help patch, the argument of pow~ should initiate the right inlet, but it doesn't seem to work.
according to the source-code, [pow~] simply ignores any creation arguments (which explains why you don't get what you expect)
pleas file a bug-report at http://bugs.puredata.info/
There has been a patch on the tracker for this since February: http://sourceforge.net/p/pure-data/patches/499/
Since it describes both the problem and the solution I see no reason why you should waste your time re-reporting the problem.
If you use Ubuntu I'd suggest using Pd-l2ork: http://l2ork.music.vt.edu/main/?page_id=56
Best, Jonathan
----- Original Message ----- From: IOhannes m zmoelnig zmoelnig@iem.at To: pd-list@iem.at Cc: Sent: Monday, October 28, 2013 5:09 AM Subject: Re: [PD] pow~ question
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-10-28 10:00, peiman khosravi wrote:
According to the help patch, the argument of pow~ should initiate the right inlet, but it doesn't seem to work.
according to the source-code, [pow~] simply ignores any creation arguments (which explains why you don't get what you expect)
pleas file a bug-report at http://bugs.puredata.info/
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-10-28 17:36, Jonathan Wilkes wrote:
There has been a patch on the tracker for this since February: http://sourceforge.net/p/pure-data/patches/499/
Since it describes both the problem and the solution I see no reason why you should waste your time re-reporting the problem.
nobody requested that. if a bug is already reported, simply add a message that states that you can confirm the bug ("me too").
if you encounter a problem, you might even check the bug-tracker before reporting it somewhere else (in some cases you might notice, that the bug has already been fixed!). (but personally i'm fine if you post a problem here first; just don't get pissed off if somebody - like me - tells you to use the bug-tracker)
fgmasdr IOhannes
Sure thing. I wanted to make sure that it's a bug before reporting it.
Thanks, Peiman
*www.peimankhosravi.co.uk || RSS Feedhttp://peimankhosravi.co.uk/miscposts.rss || Concert News http://spectralkimia.wordpress.com/*
On 28 October 2013 16:59, IOhannes m zmoelnig zmoelnig@iem.at wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-10-28 17:36, Jonathan Wilkes wrote:
There has been a patch on the tracker for this since February: http://sourceforge.net/p/pure-data/patches/499/
Since it describes both the problem and the solution I see no reason why you should waste your time re-reporting the problem.
nobody requested that. if a bug is already reported, simply add a message that states that you can confirm the bug ("me too").
if you encounter a problem, you might even check the bug-tracker before reporting it somewhere else (in some cases you might notice, that the bug has already been fixed!). (but personally i'm fine if you post a problem here first; just don't get pissed off if somebody - like me - tells you to use the bug-tracker)
fgmasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJSbpf8AAoJELZQGcR/ejb4qs8P/R51IC02nAgCuHORzhcV9ThM F1kLico1/ZXThHyz0oNL34zdxMqWX4Y/u5iSmhi917qFK+GNofaxVC3alTpL+BMw UgpTk3X9Auw5xZVGGLJwGkN9Qk/xOxjFJkxozJEazlBEzN/u0byxmofHIwwrYSKO yElBdWLhB9Xxvk+n9JRKw84ABHyMZ4H8Jcz5uWh4dxVPuMgwT7cokDL8DRnUwSEc 4LmPVZfEy3LZk9jDZe0QHkF3wjIKbTzonce25y3oonsXi4qFNZ00afMzSPt0WMm2 oKetOdKNronzRQoQhIiVgCBz7fK7atGttPV6K8GrXzVouWyf5so6wXOgRVxhECDY XtxQ+b49ChgFnot14iD0+I3cc1Ujwr+HL4sPoanQH4ebwMYPoP8q4YPEl65mt3yS 3OKn0oD7Nb2Zs92CkUc7oF4aQkjwI/kdGngbuOWYBaLKpN+pmx7zZ38uVE+LHYNo VehCY2Kd0xpIFmPUlmc5nXhAwhnYhev3h+YjcFPfxmKQSvz1TNGqA4mSnwfW912x 29FDBFLL7fsJMI/3fGuGZe5W+y+PkmJSQLwnXcm3KdJ/57yE1hWoPrVofOrh9vRU wcQh7+hH0Lb8wWSexU37cbbUgfjgU43b8cYXnTOYojImZbK1fi4FnW8nLiOrvG+c usO7ZTd8FxLILZ/bwNDF =RysT -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 10/28/2013 12:59 PM, IOhannes m zmoelnig wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-10-28 17:36, Jonathan Wilkes wrote:
There has been a patch on the tracker for this since February: http://sourceforge.net/p/pure-data/patches/499/
Since it describes both the problem and the solution I see no reason why you should waste your time re-reporting the problem.
nobody requested that. if a bug is already reported, simply add a message that states that you can confirm the bug ("me too").
That's also a waste of the user's time. It's not going to add anything of value to what's already there.
if you encounter a problem, you might even check the bug-tracker before reporting it somewhere else (in some cases you might notice, that the bug has already been fixed!).
Yes, the first thing one should do before posting on the list is to check the tracker for bugs/patches/feature requests.
-Jonathan
(but personally i'm fine if you post a problem here first; just don't get pissed off if somebody - like me - tells you to use the bug-tracker)
fgmasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJSbpf8AAoJELZQGcR/ejb4qs8P/R51IC02nAgCuHORzhcV9ThM F1kLico1/ZXThHyz0oNL34zdxMqWX4Y/u5iSmhi917qFK+GNofaxVC3alTpL+BMw UgpTk3X9Auw5xZVGGLJwGkN9Qk/xOxjFJkxozJEazlBEzN/u0byxmofHIwwrYSKO yElBdWLhB9Xxvk+n9JRKw84ABHyMZ4H8Jcz5uWh4dxVPuMgwT7cokDL8DRnUwSEc 4LmPVZfEy3LZk9jDZe0QHkF3wjIKbTzonce25y3oonsXi4qFNZ00afMzSPt0WMm2 oKetOdKNronzRQoQhIiVgCBz7fK7atGttPV6K8GrXzVouWyf5so6wXOgRVxhECDY XtxQ+b49ChgFnot14iD0+I3cc1Ujwr+HL4sPoanQH4ebwMYPoP8q4YPEl65mt3yS 3OKn0oD7Nb2Zs92CkUc7oF4aQkjwI/kdGngbuOWYBaLKpN+pmx7zZ38uVE+LHYNo VehCY2Kd0xpIFmPUlmc5nXhAwhnYhev3h+YjcFPfxmKQSvz1TNGqA4mSnwfW912x 29FDBFLL7fsJMI/3fGuGZe5W+y+PkmJSQLwnXcm3KdJ/57yE1hWoPrVofOrh9vRU wcQh7+hH0Lb8wWSexU37cbbUgfjgU43b8cYXnTOYojImZbK1fi4FnW8nLiOrvG+c usO7ZTd8FxLILZ/bwNDF =RysT -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
OK thanks,
I'm on os x but this is hardly a crippling issue! loadbang and a message box will do for now.
Thanks Peiman
*www.peimankhosravi.co.uk || RSS Feedhttp://peimankhosravi.co.uk/miscposts.rss || Concert News http://spectralkimia.wordpress.com/*
On 28 October 2013 16:36, Jonathan Wilkes jancsika@yahoo.com wrote:
There has been a patch on the tracker for this since February: http://sourceforge.net/p/pure-data/patches/499/
Since it describes both the problem and the solution I see no reason why you should waste your time re-reporting the problem.
If you use Ubuntu I'd suggest using Pd-l2ork: http://l2ork.music.vt.edu/main/?page_id=56
Best, Jonathan
----- Original Message ----- From: IOhannes m zmoelnig zmoelnig@iem.at To: pd-list@iem.at Cc: Sent: Monday, October 28, 2013 5:09 AM Subject: Re: [PD] pow~ question
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2013-10-28 10:00, peiman khosravi wrote:
According to the help patch, the argument of pow~ should initiate the right inlet, but it doesn't seem to work.
according to the source-code, [pow~] simply ignores any creation arguments (which explains why you don't get what you expect)
pleas file a bug-report at http://bugs.puredata.info/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJSbimrAAoJELZQGcR/ejb4998QAJbUXWRcIzAbrzepiQUZTzj3 GLNtGWFLG4JgJEmjemDZpWp7yhHrzB6meaIxX+F/GFXrzv5/CSzD/C/iJgyUjM3k zscXNg8xYil8vhKHjx+pcxB+8kHiDHkNQ9BoL2nKkD9+w9mjc5TY3ILW3VpoV5Fb BR6lSrM7OjnPXy+Kr/k5XyYJUY540zkr1ImsYajADHegkb9NXwmbkVAtQ3LQbCPo A3KjFgm4THtQgR6rvCr6i4KL8u2cXspn8bclGnt6HKsUd1mBpQzBoPRUV2qIpndl hT0sEwImnmtWAC6Z/hjU0Lwsir7nbCtsi3xNtjbTBdfOsXCIatKSaPfhS2bDILWk 35VXosjB2g4JpSbU+OQjSQgOOM7Ly1PpdXtLRzVSEpCwDCyjy8cRZKfXv4iYceg2 ma3Xa+upe04xZwy3PIEWaMsIyjeTzl+SFH8MgLIc3XmCewgvINKFnWF5AEVbHRNh ZjbNByn7oN0a+6gbsBLnzKmPhw5hs6sPCeaCyuSMFgQdJBrsJqkE5X8SQu3/Xytj tsznJWInevIZyuevUB7QgAWyE7RcH6js+TK4jbrkxBys4PXngZYOI7sR2RwEPNG7 RRSTC8TPffXQfgwFEo36bi1z55pYVrdA7Ap8PyFnKRL7aNKTKJJ1lvAMN679DmYX oJpBnR57n5zwPmdyxoYf =wyjI -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Mon, Oct 28, 2013 at 10:00 AM, peiman khosravi peimankhosravi@gmail.comwrote:
According to the help patch, the argument of pow~ should initiate the right inlet, but it doesn't seem to work. (Please see the attached patch.)
[sig~] does accept creation arguments. That's a workaround.
-
Funs Seelen -
IOhannes m zmoelnig -
Jonathan Wilkes -
peiman khosravi