Ken Shmidheiser wrote:
> Alain, true to character, issues the understatement of the year:
> 
> 
>> --- snip --- I have enhanced Word Indexer a little bit.
> 
> 
> 
> Alain,
> 
> Putting me on the same page as Columbus means you must rank up there 
> with NASA!
> 
> Great job with the excellent new features-- especially drag and drop!
> 
> Just a few comments and questions:
> 
> 1. For consistency, I recommend we change all occurrences where the name 
> of the app appears, including the output file, windows and titles, to 
> either "Word Indexer" or, perhaps, the more diminutive "Wordexer" (which 
> would seem to circumvent copyright or trademark problems from a cursory 
> web search. I had considered the Latin "Index Verbum", as well as the 
> longer, more "pun-ish"-- or perhaps "punish", dependent on viewpoint-- 
> "New Word Sorter". R.C. or others on the list might have some clever 
> ideas.) During development I kept changing the name as is now reflected 
> by inconsistencies throughout the code.
> 

Wordexer seems fine by me, it sounds a bit in the same vein as 
QuiXample. WordIndy, suggested by Joe is OK too, although I would have 
missed completely the pun.

> 2. There is a window refresh problem in PPC when a sort/index on very 
> large files. When the navigation dialog is opened to find a file, it 
> clips the contents of the main window beneath it. 
<snip>
I don't remember having seen this at my side.


> 3. Another problem when working with massive text files is that the 
> progress bar appears to stall at "Sorting word list...". Again I have 
> been unsuccessful in implementing an incremental progression of the 
> progress bar while Quick Sort is doing its thing. Any help here will be 
> greatly appreciated. Perhaps we could turn the progress bar to 
> indeterminate during the sort, at least to provide the user visual 
> feedback that the app has not stalled. However, I can't get that working 
> either, At a minimum, we probably should changed the edit field message to:
> 
> "Sorting word list (this may take a few minutes on very large files)..."
> 
Actually, Word Indexer is not designed as a real app, it is rather a 
short example. But, I admit for long texts it's not really user 
friendly. To get the indeterminate state for the progress bar, you 
need to give cpu time so that IdleControl can do its job.
Updating the progress bar with an increment would have a bad impact on 
the speed. Perhaps, in a real program, I would use the PollTime 
routine by Robert Purves (like I did in QuiXample) to avoid such an 
issue.

> 4. For some reason, the 200000 default setting for _splitArraySize works 
> fine for the KJV in PPC, but needs to be set to 950000 to work in OS X. 
> I do not understand why this occurs. It would appear to me that just the 
> opposite should occur with OS X's touted superior memory management. 
> Perhaps we could add a user preference to set a higher array size for 
> very large text file sorts. Any thoughts?
> 
I don't know what to think. That sounds weird.

> 
> 7. I have rewritten the About Window function to make it more attractive 
> in PPC and more compliant with OS X's HIG. (In final builds I would like 
> to add a nice icon.)
> 

> 
> infoStr =¬
>   chr$(13) + "   A small utility to designed"¬

Shouldn't this be "A small utility designed to" ?


Alain