|
|
| Re: Storing variables in multiple widgets applications [message #41615 is a reply to message #41611] |
Fri, 05 November 2004 19:16  |
kuyper
Messages: 5
Registered: June 2004
|
Junior Member |
|
|
jesusin@gmail.com (Jes?s Dom?nguez Colino) wrote in message news:<fd04930c.0411032350.4f49322@posting.google.com>...
> James Kuyper <kuyper@saicmodis.com> wrote in message news:<418914D8.70008@saicmodis.com>...
>
>> When you have many parameters, I think you'll find that many of
those
>> parameters are specific to the component parts of your widget,
rather than
>> being specific to the top-level base. Therefore, store those
parameters in
>> the user values of the corresponding components.
>
> But when you kill these components you have to pass the parameters to
> the top-level base or store them somehow. Just imagine you need all
> the parameters for a "process button" in the top-level base.
> Greetings,
> Jes�s
If you still need the parameters after killing the component, then the
parameter isn't really related to that component. You'll have to make
it a part of the top-level base's user value, or at least store it in
a pointer or a file that are referenced from the top-level base's user
value. Sorry.
|
|
|
|
| Re: Storing variables in multiple widgets applications [message #41636 is a reply to message #41615] |
Thu, 04 November 2004 02:51 |
Antonio Santiago
Messages: 201
Registered: February 2004
|
Senior Member |
|
|
Perhaps you can encapsulate the information of every component in an
object and asociate de UVALE to that object.
"component" <----------> "Object with compnent information"
The top-level widget UVALUE can have a set of references to the object
information on every componen.
top-level <-----------> "Object component info 1"
|
|-----> "Object component info 2"
|
-----> "Object component info 3"
You can remove the component and the last information persist in the object.
It is only an idea.
Bye :)
> Jes?s Dom?nguez Colino wrote:
> Hi all,
>
> i have read many things about user values and common blocks but still
> don�t find the best solution.
>
> Imagine you have a top-level base with many children and many
> parameters each. Which is the best way to store these parameters? I am
> storing all the parameters in the user value of the top-level base,
> but i don�t think this is the best solution when you have many
> parameters. Defining common blocks is something that has also many
> disadvantages. I have thought about defining external objects or
> saving the variables to .sav files. Which is the optimal solutions?
> What do you think?
>
> Thanks in advance,
> Jes�
|
|
|
|
| Re: Storing variables in multiple widgets applications [message #41637 is a reply to message #41636] |
Wed, 03 November 2004 23:50 |
jesusin
Messages: 2
Registered: November 2004
|
Junior Member |
|
|
James Kuyper <kuyper@saicmodis.com> wrote in message news:<418914D8.70008@saicmodis.com>...
>
> When you have many parameters, I think you'll find that many of those
> parameters are specific to the component parts of your widget, rather
> than being specific to the top-level base. Therefore, store those
> parameters in the user values of the corresponding components.
But when you kill these components you have to pass the parameters to
the top-level base or store them somehow. Just imagine you need all
the parameters for a "process button" in the top-level base.
Greetings,
Jes�
|
|
|
|
| Re: Storing variables in multiple widgets applications [message #41646 is a reply to message #41637] |
Wed, 03 November 2004 09:26 |
James Kuyper
Messages: 425
Registered: March 2000
|
Senior Member |
|
|
Jes?s Dom?nguez Colino wrote:
> Hi all,
>
> i have read many things about user values and common blocks but still
> don�t find the best solution.
>
> Imagine you have a top-level base with many children and many
> parameters each. Which is the best way to store these parameters? I am
> storing all the parameters in the user value of the top-level base,
> but i don�t think this is the best solution when you have many
> parameters. Defining common blocks is something that has also many
> disadvantages. I have thought about defining external objects or
> saving the variables to .sav files. Which is the optimal solutions?
> What do you think?
When you have many parameters, I think you'll find that many of those
parameters are specific to the component parts of your widget, rather
than being specific to the top-level base. Therefore, store those
parameters in the user values of the corresponding components.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
