Wave Button setEnable(false) don't work the same as gwt button setEnable(false)

[GoogleCodeExporter]

<code>
VerticalPanel cp=new VerticalPanel();
final org.cobogw.gwt.waveapi.gadget.client.ui.Button testButton=new 
org.cobogw.gwt.waveapi.gadget.client.ui.Button();
        testButton.setText(Boolean.toString(testButton.isEnabled()));
testButton.addClickHandler(new ClickHandler(){
    @Override
    public void onClick(ClickEvent event) {
           testButton.setEnabled(!testButton.isEnabled());
testButton.setText(Boolean.toString(testButton.isEnabled()));
    }           
});

vp.add(testButton);

final com.google.gwt.user.client.ui.Button tBtn=new 
com.google.gwt.user.client.ui.Button();
tBtn.setText(Boolean.toString(tBtn.isEnabled()));
tBtn.addClickHandler(new ClickHandler(){

    @Override
    public void onClick(ClickEvent event) {
        tBtn.setEnabled(!tBtn.isEnabled());
        tBtn.setText(Boolean.toString(tBtn.isEnabled()));
    }           
});
vp.add(tBtn);
</code>

What is the expected output? What do you see instead?
the button should be disabled as the same as the second button when clicked

What version of the product are you using? On what operating system?
cobogwave 1.1.2
gwt 2.0.3
chrome
win7
Please provide any additional information below.

Original issue reported on code.google.com by monstern...@gmail.com on 29 Jun 2010 at 11:55

[GoogleCodeExporter]

there is a typo in the code
first line should be
VerticalPanel vp=new VerticalPanel();

and will there be a discussion group for people who use this?
i would like to know how do u add a X(the close button) on a wave dialog box

Original comment by monstern...@gmail.com on 1 Jul 2010 at 4:39

[GoogleCodeExporter]

I was able to reproduce the problem. Currently the wave ui widgets are not very 
stable and perfect. The problem with the button is partly because the wave ui 
widget doesn't support disabled state and the problem with the X(the close 
button) is that the wave dialog box generated code in by the wave JavaScript 
has changed and is now incompatible with the cobogwave widget, which explains 
why the X isn't shown. I'm working on improving both and letting it depend less 
on the wave library, but I've not have the time yet.

As for the forum, I'm not planning on a separate forum, but I suggest to use 
the wave api forum: http://groups.google.com/group/google-wave-api/

Original comment by hs@h72.nl on 2 Jul 2010 at 8:13

• Changed state: Accepted