Re: layout panel problem, invisible panels

That is what is so nice about it.  But generally we end up wanting to know about the resize to modify elements that are inside of the child widget either to reposition or resize them.

 

It is actually an easy fix, unfortunately the new review system isn't me friendly.  If anyone wants to take it on you basically just need to add the following code to

forceLayout():

    if (header != null && header instanceof RequiresResize) { //added
       ((RequiresResize) header).onResize();
    }

    if (footer != null && footer instanceof RequiresResize) { //added
      ((RequiresResize) footer).onResize();
    }

On Wednesday, July 10, 2013 10:32:32 AM UTC-4, Thomas Broyer wrote:

The goal of HeaderPanel is to let the header and footer use their "intrinsic size", so they shouldn't be RequiresResize widgets. Note that I don't disagree making HeaderPanel implement ProvidesResize.

Patches welcome ;-)

On Wednesday, July 10, 2013 4:00:24 PM UTC+2, Patrick Tucker wrote:

What's the harm in making it implement ProvidesResize and correctly notify all children?  I've seen this topic so many times and have had to work around it on many projects myself.

On Wednesday, July 10, 2013 5:19:23 AM UTC-4, Thomas Broyer wrote: 

The reason HeaderPanel doesn't implement ProvidesResize is because it doesn't fulfill the contract for the header and footer widgets (that's the whole design goal of HeaderPanel).

We should probably add it to the javadoc.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.