Re: avoiding jbcl?

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

Article #11781

Back to borland.public.jbuilder.java.swing Previous Next

#11781

From: Paul Franks (TeamB)
Date: Wed, 14 Apr 1999 00:00

18 lines
1044 bytes

I don't have a direct answer, but I would guess this could be a bug 
workaroundaround for the original GridbagConstraints class.  

Untested..... Can you avoid importing jbcl.* if you make an explicit 
import of GridbagConstraints2?  

mv@enator.dk says...
// The problem is, that if I use a GridbagLayout, JBuilder2 insist on
// importing JBCL in order to use its GridbagConstraints2 class.
// 
// Even if I replace this with the old GridbagConstraints, every time
// I place a new button or move an existing on around JBuilder automatically
// uses GridbagConstraints2 and imports JBCL.
// 
// 

-- 
pf

Technical Details

Message-ID: <MPG.117e8cb0812f5fe1989b75@forums.inprise.com>

Path: arc1-ca.pugleaf.net!unknown!not-for-mail

References: <7es8v5$ar04@forums.borland.com>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 111d45,adb18793a260417f
X-Google-Attributes: gid111d45,public
From: supportinfo@inprise.com (Paul Franks (TeamB))
Subject: Re: avoiding jbcl?
Date: 1999/04/14
Message-ID: <MPG.117e8cb0812f5fe1989b75@forums.inprise.com>
X-Deja-AN: 466375130
References: <7es8v5$ar04@forums.borland.com>
Organization: TeamB
Newsgroups: borland.public.jbuilder.java.swing

Reply to Parent Message