-1
>>Keep Implement and Override but have the
>>Override dialog include *all* the methods
>>that can be overridden or implemented,
>>preferably with the abstract methods
>>highlighted in some way.
IMHO, this would not be good. The override methods list should not be dirtied with methods that should be implemented, or vice versa. The 'override methods' dialog should only include methods that can be overriden.
Maybe providing a combination 'implement and override methods' dialog as a third option would be acceptable. Basically the proposed dialog would just be 'return a list of all the non-final methods from superclasses and the interfaces they implement, that are not implemented in the current class'. I would not use this dialog, however, as I am comfortable with using Implement methods, and then if necessary using Override methods.
regards,
Andrew
-----Original Message-----
From: Mark Swinkels [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 18, 2002 12:44 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [Eap-list] Issues with Latest Build IDEA on Mac OS X
How about the following. Keep Implement and Override but have the Override dialog include *all* the methods that can be overridden or implemented, preferably with the abstract methods highlighted in some way. This way I can look either at the methods I *have* to implement or at all the methods I *can* override or implement. This would save a step when starting a new class and not in any way affect the usability of the Override dialog.
-- Mark
