I think that disabling the selected tab is a valid state, as is programatically selecting a disabled tab. It should be up to the user to decide if the user should be booted off the tab if its disabled.
Thanks, John LaBanca [EMAIL PROTECTED] On Fri, Sep 19, 2008 at 10:07 AM, Joel Webber <[EMAIL PROTECTED]> wrote: > Sounds ok to me. The only caveat I would add is to think carefully about > how we handle the various states that might come up inadvertently -- for > example, what happens if you disable the currently-selected tab? > > > On Thu, Sep 18, 2008 at 9:51 PM, Emily Crutcher <[EMAIL PROTECTED]> wrote: > >> Seems like a good idea to me. >> >> On Thu, Sep 18, 2008 at 9:22 PM, John LaBanca <[EMAIL PROTECTED]>wrote: >> >>> Contributors - >>> >>> I propose adding the following method to TabBar: >>> >>>> public void setTabEnabled(int index, boolean enabled) >>>> >>> >>> When disabled, a tab will be assigned the additional style >>> "gwt-TabBarItem-disabled", and the user will not be able to select the tab >>> using the mouse or keyboard. The style themes will be updated to reflect >>> the disabled state. >>> >>> You can see the proposed patch attached. Here is the associated issue: >>> http://code.google.com/p/google-web-toolkit/issues/detail?id=2527 >>> >>> Does anyone see any problem with this enhancement? >>> >>> Thanks, >>> John LaBanca >>> [EMAIL PROTECTED] >>> >>> >>> >> >> >> -- >> "There are only 10 types of people in the world: Those who understand >> binary, and those who don't" >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
