Thank you very much, I should have looked harder for that one. Is there a list of what messages you could send to a gui object (like 'range' - are there more I could use?)? And can read out of a vslider something like a 'clicked' event?

I have a player with a vslider displaying current position, I want to drag the slider to change ('scratch'), so I only want to use the slider to update the current position if I drag it using the mouse, not when it's being updated with the current position from the player.

a clicked/dragged event would be easy to toggle blocking signals/sending them elswhere.

On Fri, 16 Jul 2004, Star Morin wrote:

in docs/5.reference/help-vslider.pd, there is a subpatch called [pd edit] should have all the info you need for this.

[bang] | [slider_name range 0 500(

On Fri, 2004-07-16 at 16:46, MvH wrote:

...

Hello, one thing I couldn't find in the docs anywhere:

I would like to update the properties ( upper and lower limits) of a number or slider inside the patch ( not by r-click and choose properties)

---

PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list

---

PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list

hello list

everytime a create the comport object it appears the following message:

RXERRORS on serial line.......

im sending numbers from a basic stamp 2 sx microcontroler to a comport object in pd. I recieve wierd numbers. if i send "9 " from my microcontroller i receive in pd : 228, 228, 228, 246, 246, 246, 246, 228, 228, 228 , 228, 228, 246, 246, etc

if i send "44" i receive : 52, 253, 52, 253, 52, 253, 36, 253, etc

if i send "i", i receive : 232, 234, 350, 248, 232, 232, 234, etc

...do anybody know why?

how can i fix this ? i want to receive the same values im sending from my microcontrollers

thanx in advance

siggmus

Use a [set $1( message before the slider when updating from the player or other objects in your patch.

I tried this, and somehow it prevents the slider from updating 'itself' through a feedback loop ( It is getting the data from the player (veejay), and sending out data to veejay to change the position when I drag the slider...). Althoug it doesn't drag very smooth yet, it seems to behave more like a gtk slider already( that is, don't update from current frame until dragging stops)

But I don't understand why?

Hallo, MvH hat gesagt: // MvH wrote:

...

...

Use a [set $1( message before the slider when updating from the player or other objects in your patch.

I tried this, and somehow it prevents the slider from updating 'itself' through a feedback loop ( It is getting the data from the player (veejay), and sending out data to veejay to change the position when I drag the slider...).

Hhm, maybe you could post a patch (excerpt) to let us see what exactly this is. "set $1" is supposed to just set the slider, without the slider outputting the value.

Ciao

Frank Barknecht _ ______footils.org__

Ok I understand: by using a message to set the new value, the slider does noet output it's new value, but if I use a number, trigger, or other slider, it outputs the value itself too. Great, this means I have a difference between what goes in and what goes out, so in case of outgoing signal I can block the ingoing signal, giving the slider a bit smoother feeling ( like scratching an LP)

Here's a bit of a patch, that has current pos on slider 1 and scratches with slider 2 to give you a bit of an idea what I'm doing. You'll need the sendVIMS thingy from http://zwizwa.fartit.com/pd/sendVIMS/ together with one of the later veejay's ( this is a very simple 'newbie' patch; i work with pd since yesterday)

#N canvas 530 103 639 525 10; #X obj 22 120 change; #X obj 73 120 change; #X msg 22 164 range $1 $2; #X floatatom 22 100 5 0 0 0 - - -; #X floatatom 73 100 5 0 0 0 - - -; #X floatatom -17 100 5 0 0 0 - - -; #X obj 22 142 pack 0 0; #X obj -7 187 hsl 250 15 459 476 0 0 empty empty empty -2 -6 0 8 -262144 -1 -1 24900 1; #X msg -221 278 video.set.frame $1; #X obj -9 208 hsl 250 15 459 476 0 0 empty empty empty -2 -6 0 8 -262144 -1 -1 8700 1; #X obj -234 92 sendVIMS; #X obj -234 61 unpack 0 0 0 0 0 0 0 0 0 0 0 0; #X msg -215 223 disconnect; #X msg -224 249 connect localhost 3490; #X text -238 11 'Video Scratcher'; #X connect 0 0 6 0; #X connect 1 0 6 1; #X connect 2 0 7 0; #X connect 2 0 9 0; #X connect 3 0 0 0; #X connect 4 0 1 0; #X connect 5 0 7 0; #X connect 6 0 2 0; #X connect 8 0 10 0; #X connect 9 0 8 0; #X connect 10 0 11 0; #X connect 11 3 5 0; #X connect 11 9 3 0; #X connect 11 10 4 0; #X connect 12 0 10 0; #X connect 13 0 10 0;

---

PD-list mailing list PD-list@iem.at to manage your subscription (including un-subscription) see http://iem.at/cgi-bin/mailman/listinfo/pd-list

hej, thanx for the info. I got something working now, that blocks off the update sigal ( going through a message ) when the slider is dragged, and sends the data to veejay to update 'current frame' ( an int) when this happens.

ugly, but functioning. though it seems to take a little time before it's running again.( less then half a second...) that's propably my dumb patch. I'll look into the matter when im finished with some other part of the project...and know more tricks... :)

On Sun, 18 Jul 2004, Frank Barknecht wrote:

Hallo, MvH hat gesagt: // MvH wrote:

...

Ok I understand: by using a message to set the new value, the slider does noet output it's new value, but if I use a number, trigger, or other slider, it outputs the value itself too.

Exactly.

...

Great, this means I have a difference between what goes in and what goes out, so in case of outgoing signal I can block the ingoing signal, giving the slider a bit smoother feeling ( like scratching an LP)

The "set" thing which works for a lot of objects is good for breaking up possible message loops. See attached patch for an example application of this.

Ciao

Frank Barknecht _ ______footils.org__