8/4/97 11:00 PM
Subject: MAX Digest - 3 Aug 1997 to 4 Aug
1997To: Recipients of MAX digests 

There are 3 messages totalling 101 lines in this issue.

Topics of the day:

  1. Peter Elsea re Time Code, etc.
  2. Grouping objects (Was: coloured patch cords)
  3. Pointer problems (external development)


Date:    Mon, 4 Aug 1997 06:57:13 -0700
From:    Christopher Dobrian 
Subject: Peter Elsea re Time Code, etc.

The following message is from Peter Elsea:

Having received several requests for my midi time code writing, I've
placed it on the server at at
You have to use fetch to get things from this site, netscape won't always

I've seen some comments about saving preferences for patches and apps. The
Lobject Larray allows filenames in its read and write commands, so you
could use it to store preferences for a patcher. Just loadbang the read and
closebang the write, and the user will never see a file dialog unless the
preferences file gets lost.

Larray is advertised as an array of floats, but the data can have any
meaning, You just have to asciize any text you need to keep.

The trick to saving preferences for an external object is to invent a

Peter Elsea
Director of Electronic Music Studios
University of California, Santa Cruz


Date:    Mon, 4 Aug 1997 10:05:51 -0400
From:    Jeremy Roberts 
Subject: Re: Grouping objects (Was: coloured patch cords)

>but there *is* a way to group objects -- Sub-Patchers.

Yes, of course. However sometimes you want to group stuff that all needs
to be visible on the top level, i.e. interface objects, etc... so if your
pointing device skips, and you un-highlight the grouped selection, you
have to re-sift-click everything.... this can get tedious!



Date:    Mon, 4 Aug 1997 16:51:01 +0200
From:    Mirko Pelgrom 
Subject: Re: Pointer problems (external development)

>Mirko Pelgrom  writeth:
>>Each open window seems to allocate about 48 bytes and a pointer to
>>it. Can this be explained? We're a bit worried about this behavior.
Tom Ritchford  wrote
>While memory leaks are troublesome, languages like C++ and C make it
>hard to avoid... and 60 bytes or so per window opening means that
>you'll lose 1 MB every 15,000 window openings.  If you opened and
>closed one window a minute, that would be 10 days worth of continuous
>Not that this shouldn't be fixed but it's probably not a big deal
>for most applications.

I'm still worried. I've been playing with MAX and zone ranger some more.
Opening a bunch of help patchers and closing them. After 5 minutes of
playing I had 104 pointers with a total of 34k of memory leaked. At this
rate you'd waste 1 MB in 2.5 hours.

Note that it's not my intention to drag down MAX or its programmers.
It's just awkward to test/debug externals with this stuff going on.

So far I've seen no answer to my second question, so I'll try again.
Is it legal, for an external, to allocate a new pointer (using
NewPtrClear()) in the init routine and release it in the Free routine.
We need a piece of static non-relocatable data for asynchronous
PNSendRequest() actions.

Any help, suggestions would be greatly appreciated.

Regards, Mirko Pelgrom

Mirko Pelgrom                                   
CDS advanced technology bv                       

|   LanBox-LC II is the low cost (about $400), AppleTalk based,     |
|   DMX-512 lighting controller/sequencer solution for MacOS(tm).   |
|   Use Hypercard, Director, MAX or LabView to synchronize/control  |
|                           lightshows...                           |
|                                                                   |
|                 Light Magic is just one click away!               |
Mirko Pelgrom
CDS advanced technology bv
"Light Magic is just one click away"


End of MAX Digest - 3 Aug 1997 to 4 Aug 1997