-
19 Mar 2012 4:32 PM #1
StretchMax longest button cut off...
StretchMax longest button cut off...
I'm pretty sure this was also happening before stretchmax broke in beta4.
Structure:
Hbox with a VBox of buttons in it. The Vbox sizes itself too small to handle the longest button.

Code:package com.citrix.client; import com.google.gwt.core.client.EntryPoint; import com.google.gwt.core.client.GWT; import com.google.gwt.resources.client.ClientBundle; import com.google.gwt.resources.client.CssResource; import com.google.gwt.user.client.ui.IsWidget; import com.google.gwt.user.client.ui.RootPanel; import com.google.gwt.user.client.ui.Widget; import com.sencha.gxt.core.client.util.Margins; import com.sencha.gxt.widget.core.client.button.TextButton; import com.sencha.gxt.widget.core.client.container.HBoxLayoutContainer; import com.sencha.gxt.widget.core.client.container.VBoxLayoutContainer; import com.sencha.gxt.widget.core.client.container.Viewport; import com.sencha.gxt.widget.core.client.container.BoxLayoutContainer.BoxLayoutData; import com.sencha.gxt.widget.core.client.container.HBoxLayoutContainer.HBoxLayoutAlign; import com.sencha.gxt.widget.core.client.container.VBoxLayoutContainer.VBoxLayoutAlign; /** * Entry point classes define <code>onModuleLoad()</code>. */ public class Beta implements IsWidget, EntryPoint { /** * The message displayed to the user when the server cannot be reached or * returns an error. */ /** * Create a remote service proxy to talk to the server-side Greeting service. */ /** * This is the entry point method. */ private BetaStyle betaStyle; private BetaResources betaResources; public interface BetaStyle extends CssResource { String button(); String buttonChange(); } public interface BetaResources extends ClientBundle { @Source("Beta.css") BetaStyle css(); } public void onModuleLoad() { RootPanel.get().add(asWidget()); } @Override public Widget asWidget() { betaResources = GWT.create(BetaResources.class); betaResources.css().ensureInjected(); betaStyle = betaResources.css(); VBoxLayoutContainer globalContainer = new VBoxLayoutContainer(VBoxLayoutAlign.STRETCH); HBoxLayoutContainer outerContainter = new HBoxLayoutContainer(HBoxLayoutAlign.STRETCH); VBoxLayoutContainer buttonContainer = new VBoxLayoutContainer(VBoxLayoutAlign.STRETCHMAX); TextButton button1 = new TextButton("button1"); TextButton button2 = new TextButton("button2"); final TextButton button3 = new TextButton("I am a Button"); BoxLayoutData buttonLayoutData = new BoxLayoutData(new Margins(5,50,5,50)); buttonContainer.add(button1, buttonLayoutData); buttonContainer.add(button2, buttonLayoutData); buttonContainer.add(button3, buttonLayoutData); buttonContainer.forceLayout(); BoxLayoutData pageData = new BoxLayoutData(new Margins(0,0,0,0)); pageData.setFlex(1); outerContainter.add(buttonContainer); globalContainer.setSize("50%", "50%"); globalContainer.add(outerContainter, pageData); Viewport viewport = new Viewport(); viewport.add(globalContainer, pageData); return viewport; } }
-
19 Mar 2012 10:41 PM #2
-
20 Mar 2012 7:31 AM #3
What browser are you noticing this issue in? I'm noticing a similar but not identical issue when running your test case, so I'll file a bug. I'll update this thread with any progress we make, but please provide some information on your test browser so we can be sure we've targeted the issue there.
-
20 Mar 2012 12:22 PM #4
There was a bug with buttons where if the text was longer than space available the button corners were cut off. This was recently fixed in SVN.
I tested your code in Firefox, Chrome, IE 6,7,8,9 and the buttons are rendered correctly.
-
28 Mar 2012 2:02 PM #5
This bug has been fixed in the Ext GWT 3.0 Release Candidate. Please upgrade your copy of Ext GWT and try your test case again. While we're confident that we've addressed this issue, please reply if you notice any continued problems after upgrading. Again, thanks for taking the time to report this bug.
-
28 Mar 2012 4:00 PM #6
-
28 Mar 2012 4:03 PM #7
-
10 Apr 2012 3:05 PM #8
any updates on this? It's still occurring in the rc
-
12 Apr 2012 4:29 PM #9
-
16 Apr 2012 12:34 PM #10
I've been able to reproduce the issue, so I've reopened the ticket and will have the team take a look. Thanks for reverifying and pointing out the regression.
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTGWT-1696
in
3.0.


Reply With Quote