Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: how to bypass this swing limit Date: Fri, 16 Sep 2011 14:48:02 -0700 Organization: Canadian Mind Products Lines: 23 Message-ID: <30h7771pbjf4inkfp8gk67t5sdcune6e71@4ax.com> References: <99d5e91e-983c-4b87-ba97-657ccf137521@glegroupsg2000goo.googlegroups.com> Reply-To: Roedy Green NNTP-Posting-Host: RCd/Ul4tyxGUBII8WGwa5g.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8092 On Fri, 16 Sep 2011 09:14:02 -0700 (PDT), Peter Cheung wrote, quoted or indirectly quoted someone who said : >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. -- Roedy Green Canadian Mind Products http://mindprod.com Your top priority should be fixing bugs. If you carry on development, you are just creating more places you will have to search for them.