Re: [PD-dev] much better scrolling algorithm (pd-extended 0.42.5)

2009-11-18 Thread Ivica Ico Bukvic
- when you select all and mouse drag components out of the current view, Pd-extended updates scrollbars immediately, Pd and Pd-devel update the scrollbars once you release the mouse, and Ico's gave me an error saying Error: can't read ::scroll(.x6d5610) - when you resize the window,

Re: [PD-dev] much better scrolling algorithm (pd-extended 0.42.5)

2009-11-18 Thread Ivica Ico Bukvic
OK, try the one below instead (with ::scroll call removed). Also, plase don't forget to do the followign test with large graphics objects and test scrollbar behavior: 1) create iemlib's number2 2) adjust its height to 60 and its font size to 50 3) drag it as far to the top as possible and what

Re: [PD-dev] namespaces for send/receive

2009-11-18 Thread Mathieu Bouchard
On Wed, 18 Nov 2009, Frank Barknecht wrote: If you use the route-approach, you can use settable routes (as an abstraction like sroute.pd in [list]-abs). But actually I have no idea why a settable receive should be necessary anyway? :) One example is the GFDP (GridFlow Documentation

Re: [PD-dev] namespaces for send/receive

2009-11-18 Thread Hans-Christoph Steiner
On Nov 18, 2009, at 2:35 AM, Frank Barknecht wrote: Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: So I guess to make it localizable, it would have to be something like framesync/fps$1. Without a settable receive, it makes this kind of chore to deal with then.

Re: [PD-dev] namespaces for send/receive

2009-11-18 Thread IOhannes m zmölnig
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hans-Christoph Steiner wrote: Why not have settable receives? iirc, the problem is that you can easily make Pd crash with settable receives. fgmar IOhannes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG

Re: [PD-dev] namespaces for send/receive

2009-11-18 Thread Frank Barknecht
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote: On Nov 18, 2009, at 2:35 AM, Frank Barknecht wrote: If you use the route-approach, you can use settable routes (as an abstraction like sroute.pd in [list]-abs). But actually I have no idea why a settable receive should

[PD-dev] netsend (and more) crash bug

2009-11-18 Thread Ivica Ico Bukvic
Hi all, In our recent troubleshooting trying to hunt down a mysterious crash at patch closing we uncovered a bug that appears to be present in pd-extended 0.41.4 and 0.42.5, as well as pd vanilla (svn checked out yesterday). Following is reproducible on Linux 9.04 Ubuntu i386. To reproduce the

Re: [PD-dev] netsend (and more) crash bug

2009-11-18 Thread Ivica Ico Bukvic
As a follow-up to this problem, manually stopping metro before closing the patch solves this problem, but that is not obviously the way to ensure someone will remember to do so every time before closing... Another correction. This problem is not apparent in pd-vanilla (even though the source

Re: [PD-dev] netsend (and more) crash bug SOLVED (patch included)

2009-11-18 Thread Ivica Ico Bukvic
Yay! Finally figured it out. Please disregard my netsend patch, it's basically treating symptoms rather than the source. It turns out that the patch I submitted before to fix canvas GOP toggle on/apply/off/apply crash has been the cause of the problem all along mainly because the final version

Re: [PD-dev] netsend (and more) crash bug SOLVED (patch included)

2009-11-18 Thread Hans-Christoph Steiner
Hey Ico, You should post this to the patch tracker once you are ready to submit it. .hc On Nov 18, 2009, at 11:40 PM, Ivica Ico Bukvic wrote: Yay! Finally figured it out. Please disregard my netsend patch, it's basically treating symptoms rather than the source. It turns out that the

[PD-dev] bug when redrawing gop within gop inside a closed sub-patch

2009-11-18 Thread Ivica Ico Bukvic
Please see attached patch. it appears whenever there is change in the gui of a closed sub-patch that has GOP sub-patch showing another GOP-ed subpatch (try reading that aloud) the redraw is attempted resulting in an error in a console. Probably the best thing is to test the attached patch. The