Community
Participate
Working Groups
I'm not too sure what the conditions of it are, but I've had this happen several times. I have a java file or xml file open in an editor and I hit Ctrl- F and it does nothing. I then went to the edit menu and the Find was grayed out. The work around fix was to do a refresh on that file and then Ctrl-F starts working again.
Ok, I think I may have just figured out when it happens. I have the open mode set to single click. If I single click on a file in the package explorer that is not already open and then do a Ctrl+F before modifying the file, it won't show the dialog. If I were to double click the file in the package explorer, it will show.
Edit/Find is a retargetable action that targets the active view or editor. Since the packages view remains active, but does not hook a handler for Find, the menu item remains disabled. You need to activate the editor first. You can do this either by clicking on it or using F12. This is a side effect of the way retargetable actions work. It is too confusing to have retargetable actions target different parts. However, it probably makes sense for Find to only target editors, never views. The current retargetable action mechanism does not support this. This could be done if the find action was contributed as a regular global action, rather than as a retargetable action, and tracked its own context (the active editor).
Ok, I tried that. I noticed that the package explorer was still highlighted and I clicked in the editor. It works for java files and highlights the editor window and Ctrl-F works. But if I single click an XML file, it opens the editor, then no matter how many times you click inside the editor it never makes it active and Ctrl-F doesn't work. If I click on the tab for the editor, it highlights and starts working.
This works with the text editor and an xml file in 20020827.
