[futurebasic] Re: [FB] CD/DVD Burner Controls: A Randy Yates Memoriam [x-fb]

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : June 2004 : Group Archive : Group : All Groups

From: Robert Covington <artlythere@...>
Date: Sat, 26 Jun 2004 05:24:19 -0400
On Saturday, June 26, 2004, at 04:53  AM, Bernie Wylde wrote:

> On 26 Jun 2004, at 03:01, Robert Covington wrote:
>
>> On Friday, June 25, 2004, at 11:44  AM, Ken Shmidheiser wrote:
>>> I have just received the sad news of Randy Yates' demise after a 
>>> single post today.
>>
>> Sounds like another one of the Bowerbird's  dumb tricks... ( 
>> Bowerbird posed as a 14 year old here, as a "Peter Dempsey" and using 
>> at least 4 other aliases to make us waste our time helping no one 
>> Real )
>
>
> Dug out my ouija board, from under the stairs, last night [that's 
> funny... I live in a bungalow?]. Anyhow, managed to contact Randy who 
> assures me he is definitely not "the bird", his post was just a 'one 
> off' and meant to be a tribute to Ken and his wonderful demos.
>
> Sorry to worry you, rc  :)
>
> bw

You frustrated Karaoke people really need another outlet. ;)

It is good that we can't kill you until TWM is at a better place 
though, so you are lucky that way. By the way, I am still having no 
luck at all getting the finder to update my custom icons...I got it so 
where it will actually replace it one time if I do a series of 
handleevents after the AE, but then not again...It's nutty. it's like I 
need the equivalent of FlushWindowBuffer for the damn file icon, but 
nothing "official" works.

I think things like this are good reasons why Apple is heading to that 
* 2.75 percent marketshare from the 2.8 they observe now. There should 
be an all-in-wonder toolbox call named simply :

FinderFlushUpdateEntireFileInfo(FSSpec/FSRef)...but sending 'fupd' 
doesn't work, and nothing else does, so again, my app will remain a 
shining example of mediocrity and a wanna-be in the basic "app-default" 
features dept. A##%@#TG.
:( :( :(

Should I just kill the file, and write a new one in it's place? Or does 
that leave danger from a botched write that wouldn't occur with a 
normal Open "O"?

* (Are we doomed as Mac'ers?)

Robert