comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: problems with passing structures around in gui widgets
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: problems with passing structures around in gui widgets [message #40400 is a reply to message #40399] Thu, 05 August 2004 13:14 Go to previous messageGo to previous message
Jeff Guerber is currently offline  Jeff Guerber
Messages: 41
Registered: July 2000
Member
On Thu, 5 Aug 2004, David Fanning wrote:

> M. Katz writes:
>
>> That's true unless the UVALUE is also a pointer. In which case you
>> don't have to "check it back" when you're done with the event handler.
>> I've found out the hard way that checking-out the state variable and
>> checking it back later can lead to some nasty conflicts when you have
>> event-driven code, multiple things going on at once, and significant
>> subroutines called from the event handler.
>
> Well, by making it a pointer I think you trade
> errors in logic for errors in syntax. :-)

Naah. You just always reference "(*info)" (including parentheses!)
instead of just "info". Everything else stays the same:

*info.data = BytArr(50, 100)
*(*info).data = BytArr(50, 100)

That's what I do. (Although instead of "info" I like to call it "statep"
(pointer to state).)

(Well, that's what I _used_ to do, until I learned how to do all this
in objects. Now it's just "self", and I don't have to check it in OR out.
Wooo!)

Jeff Guerber

* I don't speak for NASA or Raytheon! *
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Launching Another App. from IDL
Next Topic: Re: Launching Another App. from IDL

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 19:34:25 PDT 2025

Total time taken to generate the page: 0.87614 seconds