It is a bug because a feature called "search" does not return results when you search for things that you would expect to get results.I might say the bug is in your expectations, then. I can find all files with the word "pano" in them e.g. PostScript: QuickSearch does not find embedded text strings, but in the search pane "Search for files and folders named: " WILL find partial file names PROVIDED you uncheck "images only".
I have done database programming and these kinds of searches are standard fare in any well designed database.įortunately DEVELOP mode has such great new enhancements! I bought ACDSee to be first and foremost a digital asset manager, and it fails. This is pretty close to a deal breaker for me. I cannot use it to RELIABLY search for a combination of either ACDSee keywords or IPTC keywords. Tech support suggests all kinds of work-arounds but the fact remains that the search system is inconsistent at best and utterly useless at worst. Quicksearch does not find embedded text strings as the OP says, and the "Files and text" search in the Search pane is next to useless as clicking "Find All Words" returns nothing if more than one word is used.
I have been going back and forth with Tech support on search issues and I must say I'm frustrated. This really does impact my work flow on a regular basis and I routinely have to use "outside of ACDSee" ways of finding files when customers place orders that could otherwise be dealt with in seconds in ACDSee. Windows Explorer search, Google, CTRL+F for find on a web page or in a document? Could you imagine if search always worked as a begins with? You'd never find anything. Don't want to call it a bug, don't, call it a request to put the feature back the way it was in version 3 and prior or to make it work the way search works everywhere else in the world where we encounter it. I've tried these common database wildcards that would otherwise work in SQL queries: This would be less of a problem if the field supported wildcards. With too many results you can apply additional search criteria to further limit them. If you had to choose between the two, returning too many results would be less of a negative than returning zero results. This is a bug because it does not actually produce meaningful, useful results. Returning only "Florida Shoot" is incorrect and misleading. It is reasonable to expect a search for the word "Florida" for example to return: No matter which way they did it, it would be "right" half the time and would be "wrong" the other half.It is a bug because a feature called "search" does not return results when you search for things that you would expect to get results. Sometimes one wants a "contains" search, other times one wants a "starts with" search.
0 kommentar(er)
