[futurebasic] Re: [FB] Mac Finder buglet ?? (was: How FB^3 saved us $$$)

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : January 2001 : Group Archive : Group : All Groups

From: Heather Donahue <heatherd@...>
Date: Wed, 24 Jan 2001 17:01:54 -0800
At 8:50 PM +0100 on 1/24/01, lcs@... wrote:


>Hi Otto, Hi Bill,
>
>In Bill's triumphant emergency intervention with FB^3, it seems
>to me that a small Mac Finder buglet has floated to the surface:-
>
>  > Then I fed PH Convert a list of the 108 references to change,
>  > and drag-and-dropped the source code files (700+ of them,
>  > about 100-150 at a time)
>
>Now why didn't Bill just drag and drop all 700+ onto the
>PH convert icon?  A assure you it's infinitely more efficient
>than painfully selecting 150 at a time many times -- especially if
>one must not process the same file twice.
>
>The bald fact is that, on drag-and-drop'ing over 500 files,
>the Finder flops and does nothing (for me).  The quantity of data
>involved is paltry; there is really no excuse.

My dropshell program under MacOS 9.0.4 handled 1001 files easily, 
albeit locking the machine until it was done. Maybe I should look 
into making the shell more responsive.


>Lets hope we get a more robust Finder, or, better, a neat
>workaround that we can keep in mind.
>Note that a workaround is the only remedy that will apply to
>all Macs.
>
>Maybe I have the wrong interpretation and the wrong code.
>Then please show me the way.  But if I am even partly
>or potentially right, the matter is worth attention.

The latest Finder using AppleEvents seems to handle numerous files. 
I wonder what the limit is though.  The Finder was a little slow when 
deleting all those files.

>PPS. To Heather: The code for DropMany_tst illustrates
>the standard cheap method for debugging mini-apps with
>the help of alert windows. It is surely OK for FB^3.
>It is easily combined with logging.
>What more do you need?

I don't know but some people like DCon.  I don't like alert windows 
because it adds code, resources, memory and you can't do anything 
with the text.  I'd really like a step through source level debugger 
for _any_ runtime.

I bought DCon but you have to link to a static library.  We can't do 
that so it might not be usable with FB^3.  If I can find a way to do 
it I will.

-- 
Heather Donahue
-- non sum qualis eram