🚀 go-pugleaf

Jeff Marendo wrote:

> I'm looking at my code right now, and I think I'm losing my mind.  I created
> a class in JBuilder3 that extends from JPanel.  
[...]
> private void jbInit() throws Exception {
>     this.setLayout(tnSwapToolPanelLayout);
>     this.setBackground(Color.white);
>     setInsertButton(btn_insert, this);
>     ...
> 
> private void setInsertButton(JButton button, TNSwapToolPanel panel) {
>     button.setText("Insert");
>     button.setFont(new java.awt.Font("Dialog", Font.BOLD, 14));
>     button.setBorder(BorderFactory.createLineBorder(Color.black));
>     button.setBackground(Color.blue);
>     button.setForeground(Color.white);
>     button.setMnemonic('i');
>     // button.addMouseListener(cursDet);
>     this.add(button, new XYConstraints(8, 12, 67, -1));
>   }
> 
> Maybe I'm going about this the wrong way, but it seems like it should work.
> I can clearly see that the buttons aren't being added to the panel when I go
> to the 'Design' tab in JBuilder3.  ...

One of the constraints of the Designer is that it cannot execute 
methods you put in the "jbInit()" method.  The Deisgner simply
ignores your "setInsertButton()" because of the way it goes 
about its business of translating your designs into code and back

Also, think about this issue: if you made changes to the 
button in the Designer, how would it know to put that
code in your special method?  It would be great if it could be
that smart but that's asking quite a lot of a Designer which
is pretty amazingly good as it is currently.

If you need to tidy things up, you do that later, after you are satisfied
with the design.  However, that's really not a great idea because 
designs -- even the best of them -- change over time.  Perhaps if
Sun pushes forward with XML and interface design, there'll come a 
time when complete separation of interface design and "model/controller"
code is possible.  For right now, you have to live with the very few 
constraints of the Designer.


Paul Furbacher  (TeamB)