All refactoring previews show only usages that would be affected by the refactoring, not all the usages (they are shown as "References to be changed"!).
In fact, it is not possible in general case to change method return type without breaking the program. What IDEA currently does with it, is changing return type for all overriding/implementing methods. So it shows only overriding/implementing methods as references to be changed. Strictly speeking, it's not a complete refactoring because it might break the code, but is also useful in many cases. We plan to enchance it for the future releases, for example, to automatically find all places where types are not matching anymore after changing the return type. The same is true for changing parameter types. Any other suggestions are welcome. Best regards, Valentin Kipiatkov ----------------------------------------------------------- IntelliJ Software, http://www.intellij.com/ "Develop with pleasure" ----------------------------------------------------------- ----- Original Message ----- From: "Michael Kirby" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 29, 2001 3:24 PM Subject: [Eap-list] Refactoring bug > I tried to do a change-signature,where the only thing I changed was the return type > (from an int to a long). > > It stated that it couldn't find any occurances of the method. > > But if I do a find usages, it works fine. > > Idea 522, jdk 1.3.1 > > Mike > --- > [EMAIL PROTECTED] > To obtain my PGP public key, mail "SEND PUB KEY" in the > subject to "[EMAIL PROTECTED]" > > > _______________________________________________ > Eap-list mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-list _______________________________________________ Eap-list mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-list
