Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!ucbvax!unisoft!hoptoad!tim From: tim@hoptoad.uucp (Tim Maroney) Newsgroups: comp.sys.mac.programmer Subject: Re: List Bummers Message-ID: <9013@hoptoad.uucp> Date: 20 Nov 89 00:46:47 GMT References: Reply-To: tim@hoptoad.UUCP (Tim Maroney) Organization: Eclectic Software, San Francisco Lines: 30 In article es2q+@andrew.cmu.edu (Erik Warren Selberg) writes: >I'm having two weird problems using an LDEF... the first one is that it >doesn't seem to respond to an undate event.... when I select the window, the >scroll bar and all that are updated, but I can't click on it or anything. > However, when I do move the window or something, it's fine. Sort of >like a second-activation deal. HALP! -- btw, I'm using a modified TWINDOW >and TList in LSP 2.0. I've written a lot of LDEFs, and I don't remember seeing that problem. Could you describe it a bit more clearly? I'm especially puzzled about how moving the window could make a difference, since it doesn't do anything to the window contents. Vague phrases like "the scroll bar and all that" and "move the window or something" are not all that helpful. Could you give a more precise description? >#2: this is more of a "can I?" question -- can I access a pointer in an >LDEF? basically, I'd like to make a pointer and put the (ord4(ptr(xxx)) >into the list data, and then use it in the LDEF. Can I do this? How??? Sure. There are two fields in a ListRec you could use. There's a refCon and a userHandle. You could stash a pointer or handle into either one to communicate between the application and the LDEF. I recommend using the refCon. Note that you have to have both sides agree on the usage conventions, so you couldn't use this for a replacement LDEF 0 or anything similar. -- Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com "God must be a Boogie Man." -- Joni Mitchell