A little regression in Seattle:

-
A little regression in Seattle:

When you select "Search in directories" in the dialog "Find In Files" and specify "*.dfm" for the file mask, the given search string is not found. This worked perfectly up to XE8.

https://quality.embarcadero.com/browse/RSP-13825
https://quality.embarcadero.com/browse/RSP-13825

Comments

  1. Uwe RaabeFebruary 28, 2016 at 5:58 AM

    Attila Kovacs Did you try on Seattle?

    ReplyDelete
  2. Alexandre MachadoFebruary 28, 2016 at 2:05 PM

    Replace it with GExperst Grep Search and be happy. It is 1000x better in any aspect.

    ReplyDelete
  3. Alexandre MachadoFebruary 28, 2016 at 2:41 PM

    I was answering Uwe Raabe which seems to have issues searching inside DFM files, and yes, for this task GExperts is not only better but is also faster. He can use GExperts to get his work done, OR, like you seem to suggest, wait for a D10 update...

    ReplyDelete
  4. Uwe RaabeFebruary 28, 2016 at 3:10 PM

    Alexandre Machado Thanks for the suggestion, but my intention was simply to show a bug in some Seattle functionality that worked perfectly the versions before. I am aware of other tools to accomplish that task. The issue arose when someone in our German forum asked for searching in DFMs and one member suggested the IDE search functionality. We then found out that it doesn't work just in Seattle. Hence the QP entry.

    ReplyDelete
  5. Marco CantùFebruary 28, 2016 at 11:47 PM

    We'll have a look to get this fixed. We also have faster and full regex searches in our todo list.

    ReplyDelete
  6. Uwe RaabeFebruary 29, 2016 at 1:29 AM

    Marco Cantù Seems to be a duplicate of an already found internal issue. It would be great if issue https://quality.embarcadero.com/browse/RSP-13333 "Adding DFM and FMX files in the "Find In Files" / "Search all files in project" could be addressed as well.

    ReplyDelete
  7. David HeffernanFebruary 29, 2016 at 1:51 AM

    I remember this being an issue even way back in Delphi 6. I had a feeling that the issue was environmental in that the behaviour appeared different on different machines.

    ReplyDelete
  8. Lars FosdalFebruary 29, 2016 at 3:18 AM

    Can it be related to threads and current directory?

    ReplyDelete

Post a Comment