| Summary: | stepping through php files in search view fails after opening two files | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Tim Diggins <tim> | ||||
| Component: | PDT | Assignee: | PHP Core <php.core-inbox> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | silviya, wywrzal | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 185835 [details]
stacktrace from error view
Failed to mention that I had this problem occurring on the "Eclipse for PHP developers" helios download and also tried Eclipse Classic 3.6.1 and installing PDT (2.2.1) on top Looks ok now. Probably fixed indirectly. Does not reproduce on El Capitan with PDT 4.0. Closing |
Build Identifier: M20100909-0800 If I do a search for a particular phrase/string (with/without regexp, case match) and then step through the search results (in the search view) using "show next match", this will work (navigating over each found context) until you navigate to a different unopened file twice (i.e. it works for the first file opened, and for the next file opened, but not for any subsequent file needing to be opened). It will work again if you close all editor tabs or open the relevant file manually searching within other file types (e.g. js files) does not display this problem so I infer it is a problem with PDT. will add the stack trace in ErrorLog as attachment Reproducible: Always Steps to Reproduce: 1.open a workspace with a php project with plenty of php files in it, ensure all editors closed 2. Menu option: "Search/File" 3. add some text that will find many results ("$_") 4. in the search view, click the down arrow ("Show Next match") and continue to do so as the matches move. After the file changes twice, "show next match" will apparently cease to function (although the search view will change the actual area will not be displayed in the editor"). to reset/workaround, close the editors, or (workaround) open the files manually