[DogParkList] Re: duplicate - flashing MLDX

[Chuck Gould]

Don,

re:

> So you did this to yourself ?  Why not enter xxx in the call field  
> and hit return - no more flashing dot. Sheesh !
>
> If you didn't know how to clear the Previous Tab why didn't you  
> just ask instead of taking up hours and hours of bandwidth with  
> your questionable design critique ?

I seem to remember a previous email conversation we had about "why  
would someone one want to lookup a BLANK call?" Now, you are using it  
as a "feature". There is NO WAY to clear the Previous tab without  
also CLEARING the Call field.

My point in the paragraph you were commenting about was that I WANT  
the call sitting there AND a lookup done. Perhaps I should wait until  
after the contact is made to do the lookup? Or, do I have to open up  
a my old text based log and us it for scratch paper?

As for your other comments - I don't think I was getting personal  
with MY comments, however you seem to need to do so to justify your  
position.

If you do not want criticism of your design, then WHY are you making  
betas available to the public? I guess short of a kernel panic, I'll  
keep to myself.

-chuck

On Sep 30, 2005, at 0411 , Don Agro wrote:

> Hi Chuck,
>
> On 30-Sep-05, at 1:26 AM, Chuck Gould wrote:
>
>
>> Don,
>>
>> Flashing RED. RED. Not just flashing. I know I said that. I don't  
>> care about the flashing ":"'s, tho I have them off in the Mac's  
>> time preferences ;)) Also, I think it's expected that a clock  
>> would have something that tick-tocks.
>>
>
> But here we are again talking about your personal preferences - not  
> what is good or bad design.
>
>
>> Hummm - Nonsense? A bit strong, but that's ok.
>>
>
> I thought it was a fair assessment of your "critical notifications"  
> argument. Still do.
>
>
>> Yes, there are very specific rules written  about what can be  
>> flashing and/or what color(s)(Google Sematech GEM (General  
>> Equipment Model)). This is not military specs. This is specs for  
>> automated manufacturing equipment. I'm not saying this applies to  
>> a consumer PC's, only that it is a real interface design concern,  
>> depending on application.
>>
>
> Exactly ! and you have offered no proof whatsoever that it applies  
> here - just your personal preference.
>
>
>> In other words, it's not just me...
>>
>
> Ahhh but it is just you so far. The only other vote was to keep the  
> flashing red dot.
>
>
>> DXCluster activity doesn't have anything to do with what I said I  
>> was doing, not even sure how that got in there. I entered the call  
>> in the call input field, while I was trying to contact them. It  
>> stays there until I do something else or make the contact. I'm not  
>> that avid of a DX'er, so I'm not making dozens of different  
>> contacts /hr. This one was interesting to me and the conditions  
>> were highly variable, so I just left the call sitting there.
>>
>
> So you did this to yourself ?  Why not enter xxx in the call field  
> and hit return - no more flashing dot. Sheesh !
>
> If you didn't know how to clear the Previous Tab why didn't you  
> just ask instead of taking up hours and hours of bandwidth with  
> your questionable design critique ?
>
>
>> Also, ignoring something flashing isn't natural. That is EXACTLY  
>> why flashing is used to gain attention. We perceive a flashing  
>> object the same as a moving object.
>>
>
> EXACTLY - so if you have seen it and want to get rid of it - clear  
> the Previous Tab. How hard can that be ?
>
>
>> I was using the term "mission critical" sort of tongue-in-cheek.  
>> NOTE the quotes.
>>
>
> Well then it isn't mission critical is it. It's just your personal  
> preference and all the lofty design standards you are quoting were  
> an attempt to lend authority to a "weak" argument ? (NOTE the  
> quotes which can mean anything I say they do after the fact if this  
> point is discounted for lacking logic).
>
>
>> I think the horse is dead. It is an ex-horse. ;)
>>
>
> I keep hoping - but emails about it keep popping into my in folder.
>
>
> 73 Don Agro VE3VRW
>
> D o g   P a r k   S o f t w a r e   L t d .
>
> email: dagro at dogparksoftware.com
>   www: http://www.dogparksoftware.com
>     iChat AV:dogpark at mac.com
>
>
>