🚀 go-pugleaf

William Yu wrote:

> Situation: the component can determine the font *after* it has been
> added to the container and then change the dimensions.  However, the
> container uses the initial dimensions to determine position and such.
> Since I doubt I can break apart the "add" routine, my guess would be to
> force the container's layout manager to re-run after the size has been
> set.  Anyone have any ideas?

Silly me.  I can't believe I not only missed this but let it go for 2
months.  My code looked like the following:

    public void addNotify() {
        setComponentSize();
        super.addNotify();
    }

But it's obvious why that code doesn't work.  Since I can't get the font
until after the component has been added to the container, the two commands
are in reverse sequence.  What was throwing me off was that doLayout() as
not working either.  What I also attempted was:

    public void doLayout() {
        setComponentSize();
        super.doLayout();
    }

My thinking this code would get the fontmetrics and set the component size
before the layout manager did its work.  But it's obvious (since the code
didn't work) this method is called after the layout manager does its work.