Login | Register
My pages Projects Community openCollabNet

Discussions > dev > [gef-dev] Why shouldBeEnabled() on Cmd?

Discussion topic

Back to topic list

[gef-dev] Why shouldBeEnabled() on Cmd?


Author bob dot tarling at ntlworld dot com
Full name bob dot tarling at ntlworld dot com
Date 2004-02-18 03:12:25 PST
Message Just reading through issue 1970 at ARgoUML http://argouml.tigri​s.org/issues/show_bu​g.cgi?id=1970 I've been prompted to ask a question that I've asked myself many times in the past.

Why is there a method shouldBeEnabled(boolean) on Cmd when Cmd extend AbstractAction which has the method setEnabled(boolean).

I presume this is due to GEF originally being pre Java2 where actions weren't tied to JButtons quite so easily.

I think the use of shouldBeENabled now causes extra unneeded framework complications.

AM I missing something or should these methods now be deprecated in favour of setEnabled()? Calling setEnabled should enabled/disable any button or menu item etc registered with that action.


Email provided by http://www.ntlhome.com/

To unsubscribe, e-mail: dev-unsubscribe at gef dot tigris dot org
For additional commands, e-mail: dev-help at gef dot tigris dot org

« Previous message in topic | 1 of 1 | Next message in topic »


Show all messages in topic

[gef-dev] Why shouldBeEnabled() on Cmd? bob dot tarling at ntlworld dot com bob dot tarling at ntlworld dot com 2004-02-18 03:12:25 PST
Messages per page: