comp.lang.idl-pvwave archive: archive » Re: GUI and non-GUI objects in Catalyst

Home » Public Forums » archive » Re: GUI and non-GUI objects in Catalyst

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

Catalyst Object Widget Hierarchy [message #69038 is a reply to message #68794]

Wed, 16 December 2009 15:38

Jean-Paul Davis
Messages: 17
Registered: March 1998

Junior Member

David,

Thought I'd keep this discussion here since my next question is so
closely related: what is the purpose of the WidgetBase::ADD and
WidgetAtom::ADD methods? When creating an object widget hierarchy
using Catalyst, I see in your examples that you simply create the
individual widget objects from within the top-level object's INIT or
GUI method, using named variables for the object references only when
needed as the parent argument to a child widget or as a property of
the top-level object. Would there ever be any reason to "ADD" child
widget objects to parent widget objects?

I know you've been asked before, but do you think there's even a
remote chance that someone (you, Burridge, or even someone else) might
ever write a book on how to use Catalyst?

Jean-Paul

Report message to a moderator

[Message index]

		Re: GUI and non-GUI objects in Catalyst By: Jean-Paul Davis on Fri, 04 December 2009 15:49
		Re: GUI and non-GUI objects in Catalyst By: David Fanning on Wed, 02 December 2009 16:00
		Catalyst Object Widget Hierarchy By: Jean-Paul Davis on Wed, 16 December 2009 15:38

Previous Topic:	Export Bridge Assistant Warning - routine could not be resolved
Next Topic:	Need to use GRIDDATA instead of CONGRID?

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Apr 27 13:48:39 PDT 2026

Total time taken to generate the page: 0.64261 seconds