🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: borland.public.jbuilder.java.swing
Article #9622

Component initialization problems

#9622
From: Jeff Marendo
Date: Tue, 22 Feb 2000 00:00
35 lines
2606 bytes
Hello,

I'm not sure where to begin on this, but I'll try to keep it concise.  I
have an applet that extends from JApplet.  It has a JTabbedPane on it.
There are about 5 tabs in all.  Each tab has its own, unique JPanel
associated with it.  There is code in place within the applet in a
stateChanged method, basically it says when I click on tab1, set tab1 to
visible and setVisible(false) for all of the others.  Clicking on the other
tabs works similarly.

My class I'm working on extends from JPanel and is one of the panels
associated with one of the tabs.  Within my class in my jbInit function, I
set a bunch of properties and add my components to "this".  After adding my
components to the class itself, part of my initialization process includes
making some IDL function calls that retrieves info from our server.  I have
try and catch statements as well as null-checking statements inside each one
of my methods that invokes a server method.  Basically, if something
returned is null, the function returns so my class doesn't bomb during the
initialization.  This info is used to value various components (like a
JComboBox, JTextField, etc.).

The problem that I'm seeing is that ANYTIME ANY one of my IDL functions
return null or fail, my code for that informs me of such circumstances,
errors from Visibroker reaffirm those conditions, and the applet loads.
However, at that point, only when I click on the tab with my class does it
not paint properly.  I can click on any one of the other tabs and their
panels show up just fine.  I click mine and either the panel from the last
tab is sitting there looking at me or some of my components show through.  I
understand how conflicts can arise from mixing lightweight and heavyweight
components together, but we're using all Swing components; and, again, I
only see this problem when one of the IDL functions fail.

Without making this any longer by posting code (that's my next step, I
think), does anyone have an idea why this behavior might be happening?
Thanks in advance.
Technical Details
Message-ID: <88v0ql$5ji4@bornews.borland.com>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 111d45,b335ff2bac01f74d,start
X-Google-Attributes: gid111d45,public
From: "Jeff Marendo" <marendoj@commos.com>
Subject: Component initialization problems
Date: 2000/02/22
Message-ID: <88v0ql$5ji4@bornews.borland.com>
X-Deja-AN: 588574102
X-Priority: 3
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Organization: CommTech Corporation
X-MSMail-Priority: Normal
Reply-To: "Jeff Marendo" <marendoj@commos.com>
Newsgroups: borland.public.jbuilder.java.swing