Bug 28771 - [Refactoring] Inline Local Variable not possible on MacOS X
Summary: [Refactoring] Inline Local Variable not possible on MacOS X
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P2 normal (vote)
Target Milestone: 2.1 M5   Edit
Assignee: Andre Weinand CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-20 14:58 EST by Boris Pruessmann CLA
Modified: 2002-12-23 08:56 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Pruessmann CLA 2002-12-20 14:58:06 EST
Build I2002-12-18

Using the "Inline Local Variable" refactoring is not possible because the "OK" and 
"Cancel" buttons are disabled although the refactoring would be possible.
Comment 1 Andre Weinand CLA 2002-12-20 16:25:08 EST
Are the buttons accessed by position?
(On Mac OS X the default button is moved to the far right, so the button's indexes are 
different than on other platforms)
Comment 2 Andre Weinand CLA 2002-12-23 04:13:48 EST
Cannot reproduce in M4 on MacOS X
Comment 3 Boris Pruessmann CLA 2002-12-23 05:20:12 EST
But not for me :( After using Refactor->Inline in M4, the new refactoring UI 
appears with both buttons disabled. Only closing the window is possible. In 
fact, everything seems to be disabled. I cannot use the arrow buttons to 
navigate throught the changes. I cannot even use the scrollbars although the 
controls accept keyboard input.
Comment 4 Dirk Baeumer CLA 2002-12-23 05:52:31 EST
Does Inline local always reveal this behaviour ? Or is it a special case
Comment 5 Boris Pruessmann CLA 2002-12-23 08:08:21 EST
Happens always, even when trying to inline test in the following example:

public class Test
{
    public static void main(String[] args)
    {
        String test = "test";
        System.out.println(test);
    }
}
Comment 6 Andre Weinand CLA 2002-12-23 08:56:47 EST
OK, I was wrong: I wasn't on M4 but on HEAD.
And I cannot reproduce the problem on HEAD (because one fix after M4 is related to this 
problem).