[Openmcl-devel] issues with search-files dialog
arthur.cater at ucd.ie
Thu Oct 13 19:20:47 UTC 2016
Thank you Paul for the (partial) affirmation, diagnosis and remedy.
> On Oct 13, 2016, at 6:16 PM, Paul Krueger <plkrueger at comcast.net> wrote:
> I’ve run into this behavior (a and c) and I believe it is caused by entering a search string and then clicking the search button without first exiting the search string field. In theory the dialog window should ensure that when the button is pushed that every field entry is finalized so that the new search string is actually read, but it clearly does not do that. Thus you get the results from the previous string, which if null matches every line in all files. So this is a bug in the interface code for this window. The work-around is just to be sure to tab out of a field before hitting the search button. I don’t believe that I’ve seen the behavior you describe in b.
>> On Oct 13, 2016, at 12:06 PM, Arthur Cater <arthur.cater at ucd.ie> wrote:
>> Hello, me again but different issue.
>> On my Macbook Pro with OS X.11.5, using the search-files dialog (via cmd-shift-f) is sometimes behaving oddly.
>> a) conducting a second search, changing the search string, sometimes does not displace the results of the first search.
>> b) conducting a second search, sometimes causes the window to shrink to around a third of its previous size, trying to resize it causes it then to become around two thirds of its previous size.
>> c) doing a search of ccl sources sometimes behaves as I’d expect, and sometimes claims to find hundreds of thousands of matches, expanding results shows that every line of a file is present as a match.
>> I attach a screenshot of a newly-started run with
>> ./dx86cl64 —no-init
>> (require :cocoa)
>> and a search.
>> <Screen Shot 2016-10-13 at 5.36.10 PM.png>
>> Should I write one or more ticket?
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
More information about the Openmcl-devel