how to bypass this swing limit

[Peter Cheung]

Dear All
how to by pass this swing limit:
Each GUI component can be contained only once. If a component is already in a container and you try to add it to another container, the component will be removed from the first container and then added to the second.

thanks
from Peter ([email protected])

 

[Daniele Futtorovic]

Dear All
how to by pass this swing limit:
Each GUI component can be contained only once. If a component is already in a container and you try to add it to another container, the component will be removed from the first container and then added to the second.

Create a new component.

If you want the components to share state, then you ought to put that
state in a model object and make the components share the same model.
State should not be stored in the view anyway.

 

[Peter Cheung]

share the model can make two components display the same data. Except this, i need to create two set of event to handle mouse click, it is quite trouble.

thanks

 

[Daniele Futtorovic]

share the model can make two components display the same data. Except
this, i need to create two set of event to handle mouse click, it is
quite trouble.

thanks

If you have, as you should, written a view/controller class that
initialises its layout, data and listeners, then the net difference
between one and two of those is one instantiation and addition to a
container.

It sounds like the design of your mouse event handler isn't right.

 

[David Lamb]

share the model can make two components display the same data. Except this, i need to create two set of event to handle mouse click, it is quite trouble.

You originally wanted the same component in two containers. If the
container handles mouse clicks, and uses them to update the model state,
why do you need two sets of events? Only one of the two components is
going to get an incoming event at any one time.

 

[Roedy Green]

Dear All
how to by pass this swing limit:
Each GUI component can be contained only once.
If a component is already in a container and you try to add it to another container,
the component will be removed from the first container and then added to the second.

The obvious answer is clone the component, and make sure you keep them
up to date with the same state, e.g. by inventing a virtual component
that you update that in turn updates a list of clones for you.

Be careful with this kind of logic you don't create endless
notification loops.

 

[Peter Cheung]

thanks everybody
Peter