At 8:47 AM -0800 1/15/2001, Irv Kalb wrote:
>Each castlib can contain 65536 member. For backwards compatibility
>reasons with D4 (remember "Shared.cst"), the first castlib
>(internal) is considered castlib #0, while the second castlib is
>considered castlib #2.
Hi Irv -
thanks! I was checking the number of member to see why some scripts
were failing in setting the member. The project is fairly complex
with a long ancestor chain and an MIAW. The odd thing is that with a
"put" statement I was seeing the number of member for the "down"
state for a button as 2 and the "up" state as 327750. This was
occurring in an MIAW and the up state was not appearing, and the
mouse up event not getting called.
What seems to have fixed it was putting a "tell the active window" in
each ancestor (there are like 3 or 4 that receive and pass the mouse
events. I would have thought that one would have been enough to set
the event context.
-Roy
--
Roy Pardi
---------------------------------------------------------------
Contract Multimedia Developer + Lingo Programmer
[EMAIL PROTECTED]
---------------------------------------------------------------
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
