Nice button style, Danny. However if you don't want to handle the
onHistoryChanged-Event - well just don't: set the hyperlink's token to
something like "dont_handle_this_token" and don't handle it ;-) But
the button-hyperlink idea is somehow cleaner.
On 27 Nov., 16:10, "Danny Schimke" <
schimk...@googlemail.com> wrote:
> You are right: it calls the onHistoryChanged- Event. Thats why we created a
> new button-Widger which extends from Button with only one difference: it has
> a different link style by default (looks like a link). Then you don't call
> onHistoryChanged- method. On Button- Click you can add or remove an style
> name which changes the color of your link-button to gray (look disabled).
>
> CSS for your link-button should look something like this:
> .button-link {
> cursor: pointer;
> cursor: hand;
> border: none;
> /* Disable the button-style */
> background-color: transparent;
> padding: 0px;
> color: #4784C3;
> text-decoration: underline;
>
> }
>
> 2008/11/27 Litty Preeth <
preeth.h...@gmail.com>
>
> > But even if you remove the clickListener, it will cause an onHistroryChange
> > event right?
>
> > On Thu, Nov 27, 2008 at 1:08 PM, Danny Schimke <
schimk...@googlemail.com>wrote:
>
> >> Should'nt setVisible() do this for HyperLinks too?
>
> >> setVisible needs an element and boolean:
>
> >> myHyperLink.setVisible(myHyperLink.getElement(), false);
>
> >> otherwise do what alex.d says:
>
> >> add and remove a style name which do this.
> >> CSS: visibility: hidden;
>
> >> 2008/11/27 alex.d <
alex.dukhov...@googlemail.com>