Hi all,
This pertains to pd-extended 0.40.3. It appears that when a patch has a very busy GUI (as is the case with wiimote help file), after a while the GUI stops being responsive. The objects can be still moved and even atoms can be written into, but when one presses "return" to update atom value or when an atom or a slider needs to change due to automated update (e.g. via metro) nothing happens until pd is restarted. The sound engine and control mechanisms running through these still work and are responsive, it is just that gui remains totally frozen. Not sure if this only pertains to the wiimote object or other busy patches as well.
Any ideas?
Ico
Hallo, Ivica Ico Bukvic hat gesagt: // Ivica Ico Bukvic wrote:
This pertains to pd-extended 0.40.3. It appears that when a patch has a very busy GUI (as is the case with wiimote help file), after a while the GUI stops being responsive. The objects can be still moved and even atoms can be written into, but when one presses "return" to update atom value or when an atom or a slider needs to change due to automated update (e.g. via metro) nothing happens until pd is restarted. The sound engine and control mechanisms running through these still work and are responsive, it is just that gui remains totally frozen. Not sure if this only pertains to the wiimote object or other busy patches as well.
It can happen in general. Updating GUI objects too often (i.e. faster than the eye can see) should be avoided in general. Passing messages through GUI sliders even is buggy in Pd: sliders may change the incoming values so what comes out is not the same as what came in (there is an open bug report regarding this on SF.)
So while a better GUI handling would be nice, it's currently better to stay defensive and change the patch to limit updates with something like change, metro, speedlim and/or RjDj's m_speedlimit.
Ciao
Frank
I think that this is a known bug that was fixed in Pd-vanilla 0.42. A
backport might be a possibility. Try 0.42 and see if it fixes your
problem.
.hc
On Mar 28, 2009, at 12:59 PM, Ivica Ico Bukvic wrote:
Hi all,
This pertains to pd-extended 0.40.3. It appears that when a patch
has a very busy GUI (as is the case with wiimote help file), after a
while the GUI stops being responsive. The objects can be still moved
and even atoms can be written into, but when one presses "return" to
update atom value or when an atom or a slider needs to change due to
automated update (e.g. via metro) nothing happens until pd is
restarted. The sound engine and control mechanisms running through
these still work and are responsive, it is just that gui remains
totally frozen. Not sure if this only pertains to the wiimote object
or other busy patches as well.Any ideas?
Ico _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Programs should be written for people to read, and only incidentally
for machines to execute.
- from Structure and Interpretation of Computer Programs
-
Frank Barknecht -
Hans-Christoph Steiner -
Ivica Ico Bukvic