On Wed, 15 Mar 2006, Roman Haefeli wrote:
hi "Chuckk Hubbard" badmuthahubbard@gmail.com wrote:
Is it possible to resize or scroll a window automatically?
i assume not, at least i couldn't find any documentation.
There is a newer version of Damien Henry's pd-msg docs in CVS, and its also included in Pd-extended. I've been maintaining it thru the years...
.hc
This one? There are two files that say they are 5 weeks old, the rest are 3 years. http://cvs.sourceforge.net/viewcvs.py/pure-data/doc/additional/pd-msg/
On Mar 21, 2006, at 7:07 AM, Chuckk Hubbard wrote:
On Wed, 15 Mar 2006, Roman Haefeli wrote:
hi "Chuckk Hubbard" badmuthahubbard@gmail.com wrote:
Is it possible to resize or scroll a window automatically?
i assume not, at least i couldn't find any documentation.
There is a newer version of Damien Henry's pd-msg docs in CVS, and
its also included in Pd-extended. I've been maintaining it thru the
years....hc
This one? There are two files that say they are 5 weeks old, the rest are 3 years. http://cvs.sourceforge.net/viewcvs.py/pure-data/doc/additional/pd-msg/
That's the one. I only changed what need changing. I see 9 changed
files, but who's counting ;)
.hc
who is in charge about coordinating tcl/tk and pd? only Mr. Puckette? I
guess that an option to query objects for their parameters would really
speed up and enhance interface design in pd. something like "; myhslider
get_width". currently it can only be used to get the coordinates of a
canvas.
Am 22.03.2006, 03:13 Uhr, schrieb Hans-Christoph Steiner hans@eds.org:
On Mar 21, 2006, at 7:07 AM, Chuckk Hubbard wrote:
On Wed, 15 Mar 2006, Roman Haefeli wrote:
hi "Chuckk Hubbard" badmuthahubbard@gmail.com wrote:
Is it possible to resize or scroll a window automatically?
i assume not, at least i couldn't find any documentation.
There is a newer version of Damien Henry's pd-msg docs in CVS, and its also included in Pd-extended. I've been maintaining it thru the
years....hc
This one? There are two files that say they are 5 weeks old, the rest are 3 years. http://cvs.sourceforge.net/viewcvs.py/pure-data/doc/additional/pd-msg/
That's the one. I only changed what need changing. I see 9 changed
files, but who's counting ;).hc
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
who is in charge about coordinating tcl/tk and pd?
there is no-one in charge
guess that an option to query objects for their parameters would really
speed up and enhance interface design in pd. something like "; myhslider
get_width"
i think this reflective nature for objects is in the design spec for DesireData (look for the PS published for Piksel '05, or the earlier one for PD-C 1.0). im pretty sure it hasnt reached the point of stability that it is being considered to be rolled into the the mainline version of PD maintained by the original author. one thing that could help change that is for you to test it out.. it is in the devel_0_39 branch of CVS
a nice interactive property inspector can be done up in 10 lines of Tk..
in desireData, the object properties are stored in a hash with keys like $_(objectID:property), in ixpd, theyre stored in a TCL dictionary
if what you want is the ability to query any object (including the core, non-GUI ones) for their current state, and set any properties via an inspector, this doesnt quite exist (although with the class inspector from impd you could probably get close to at least knowing what stuff is changeable, without digging thru the help patches or object source)
pd is still a work in progress...
On Mar 22, 2006, at 4:03 AM, cdr wrote:
who is in charge about coordinating tcl/tk and pd?
there is no-one in charge
guess that an option to query objects for their parameters would
really speed up and enhance interface design in pd. something like ";
myhslider get_width"i think this reflective nature for objects is in the design spec
for DesireData (look for the PS published for Piksel '05, or the
earlier one for PD-C 1.0). im pretty sure it hasnt reached the
point of stability that it is being considered to be rolled into
the the mainline version of PD maintained by the original author.
one thing that could help change that is for you to test it out..
it is in the devel_0_39 branch of CVSa nice interactive property inspector can be done up in 10 lines of
Tk..in desireData, the object properties are stored in a hash with keys
like $_(objectID:property), in ixpd, theyre stored in a TCL dictionaryif what you want is the ability to query any object (including the
core, non-GUI ones) for their current state, and set any properties
via an inspector, this doesnt quite exist (although with the class
inspector from impd you could probably get close to at least
knowing what stuff is changeable, without digging thru the help
patches or object source)pd is still a work in progress...
It'd be nice to see some kind of binary release of DesireData so we
can play without compiling and all that. Do any exist?
.hc
As we enjoy great advantages from inventions of others, we should
be glad of an opportunity to serve others by any invention of ours;
and this we should do freely and generously.
- Benjamin Franklin
who is in charge about coordinating tcl/tk and pd?
there is no-one in charge
guess that an option to query objects for their parameters would really speed up and enhance interface design in pd. something like "; myhslider get_width"
i think this reflective nature for objects is in the design spec for DesireData (look for the PS published for Piksel '05, or the earlier one for PD-C 1.0). im pretty sure it hasnt reached the point of stability that it is being considered to be rolled into the the mainline version of PD maintained by the original author. one thing that could help change that is for you to test it out.. it is in the devel_0_39 branch of CVS
a nice interactive property inspector can be done up in 10 lines of Tk..
in desireData, the object properties are stored in a hash with keys like $_(objectID:property), in ixpd, theyre stored in a TCL dictionary
if what you want is the ability to query any object (including the core, non-GUI ones) for their current state, and set any properties via an inspector, this doesnt quite exist (although with the class inspector from impd you could probably get close to at least knowing what stuff is changeable, without digging thru the help patches or object source)
pd is still a work in progress...
For mouse clicks: 1-shift 2-control 3-shift-control 4-alt 5-shift-alt 6-ctrl-alt 7-shift-ctrl-alt 8-right click
For mouse and mouseup, $3 tells which mouse button is pressed. Mouseup, obviously, leaves off the 4th field, as it doesn't matter whether you're still holding shift when you release. I'm not sure all of these 8 would be useful as messages, but there they are. A 1 as the last field in a key message means shift is pressed. Control and Alt don't seem to change anything.
I'm anxious to hear if anyone figures out [relocate(, I can't get anything from it.
-Chuckk
On 3/21/06, Hans-Christoph Steiner hans@eds.org wrote:
On Mar 21, 2006, at 7:07 AM, Chuckk Hubbard wrote:
On Wed, 15 Mar 2006, Roman Haefeli wrote:
hi "Chuckk Hubbard" badmuthahubbard@gmail.com wrote:
Is it possible to resize or scroll a window automatically?
i assume not, at least i couldn't find any documentation.
There is a newer version of Damien Henry's pd-msg docs in CVS, and its also included in Pd-extended. I've been maintaining it thru the years...
.hc
This one? There are two files that say they are 5 weeks old, the rest are 3 years. http://cvs.sourceforge.net/viewcvs.py/pure-data/doc/additional/pd-msg/
That's the one. I only changed what need changing. I see 9 changed files, but who's counting ;)
.hc
-
cdr -
Chuckk Hubbard -
future rage
-
Hans-Christoph Steiner -
João Miguel Pais