🚀 go-pugleaf

Hi folks,

I've run into a problem while using more than two DPSTimedEntries...

I'm setting up a program that samples data from the DSP and subsequently  
displays it in multiple views (ten to be exact). I'm using a single  
DPSTimedEntry to call the routine that samples data from the DSP and a  
DPSTimedEntry to call the display routine for each view (one entry per  
view)... hence, eleven DPSTimedEntries in all.  I do this to distribute  
the display of the views, so that I don't have large gaps in the sampling  
of the DSP.

Anyway, the DPSTimedEntry for sampling the DSP sets up fine, as does the  
one for my first view that I'm displaying in... but the subsequent 9  
DPSAddTimedEntry calls return "0" (not "-1" as the documentation says it  
should in the event of an error). The display objects/code are contained  
in a nib file that I load at run time for each of my 10 views(windows), so  
I'm pretty sure that I'm doing everything identically for each of the  
views... but only the first one works.

Is there a limit to the number of timed entries that an application can  
have?  Has anyone run into this problem before?

Thanks,
Robert Kieffer
kieffer@spf.trw.com