comp.lang.idl-pvwave archive: archive » Interactive Graphics Library

Home » Public Forums » archive » Interactive Graphics Library

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Interactive Graphics Library [message #80279 is a reply to message #80176]

Thu, 24 May 2012 08:36

Raphael Sadoun
Messages: 4
Registered: May 2012

Junior Member

On May 23, 3:34 am, Russell Ryan <rr...@stsci.edu> wrote:
>
> So, I was looking at the code. Can either of you two explain the
> virtues of writing a GUI as an object?

Well, one of the basic principle of the Interactive Graphics Library
is that
all the graphics displayed in the window constitute an object tree
hierarchy with the window object
at the top. So the main advantage for writing the window as an object
was to benefit the automatic
memory management that the catalyst library provides with the CATATOM
class (using reference couting).
This is really needed in order to avoid memory leakage when using an
object-oriented framework like the IGL which can potentially
creates a LOT of objects!

Now, it is also generally easier to write widget applications (GUI) as
objects since the state of the
application can be stored directly with the object (class arguments)
instead of using a pointer to a
structure (often referred as the "info" structure).

Cheers

Raphael

Report message to a moderator

[Message index]

		Interactive Graphics Library By: Raphael Sadoun on Sat, 12 May 2012 02:18
		Re: Interactive Graphics Library By: Russell Ryan on Mon, 21 May 2012 12:26
		Re: Interactive Graphics Library By: Russell Ryan on Tue, 22 May 2012 18:34
		Re: Interactive Graphics Library By: Raphael Sadoun on Thu, 24 May 2012 08:36

Previous Topic:	Re: Subscription 'daily digest' problems?
Next Topic:	Type of array to store large numbers

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Oct 09 15:25:28 PDT 2025

Total time taken to generate the page: 2.15739 seconds