Friday, July 14, 2000, 9:55:00 AM, Januk wrote:
>>     First, a simple change.  Make it possible for threads to be expanded by
>> default upon entering a folder.

> I would be ambivalent to this suggestion.

    Which is why its wording is "possible" denoting it as an option, not a
standard behavior.

> I can see how it might be useful for your purposes. However, for me, the way
> TB bolds all messages higher than the unread message is more convenient.

    I find that utterly worthless.  I can see how others can find it useful so
it should remain, but to me it is an annoyance that gets in the way of reading
mail.

> I find that by placing the focus on the first message in the thread
> and hitting Ctrl-], the digging is eliminated.

    Unless you mark things unread again to know you still need to look at
them.  Or when you want to read one branch of a thread but not another.  Or
most likely another dozen examples I've not thought of.

>  The expand all threads key is indeed Ctrl-(Numpad)*.

    No, it is not.  It is CNTL-*.  How that * is inputted is meaningless so I
fail to see why people insist on denoting the Numpad.

> Short of allowing remappable shortcuts, how can RITLabs accommodate every
> individual computer setup (software or hardware)?

    Which is why most modern 'nix clients have remappable keys, even when they
weren't modern, and why people are clammering for remappable keys.

>  since TB doesn't really remove the message from the messagebase right
>  away, perhaps deleted messages could still affect threading as though
>  they weren't marked for deletion.  However I could see this becoming
>  a bit of a security issue, not to mention an implementation
>  nightmare.

    Ah, this is why I asked to see the original since Ming-Li didn't quote
this part in her reply.  Yes, the messages are still there.  I don't see why
it is is a security nightmare.  Windows itself is a security nightmare.  When
someone has physical possession of your computer it is a security nightmare.
Having messages in the message list that are marked as deleted doesn't present
any real risk.

    Implementation should be simple.  Take the flag, toss it out the window,
make that field "marked for deletion", don't remove it from the list upon
deletion, make it an option.

-- 
         Steve C. Lamb         | I'm your priest, I'm your shrink, I'm your
         ICQ: 5107343          | main connection to the switchboard of souls. 
-------------------------------+---------------------------------------------

-- 
--------------------------------------------------------------
View the TBBETA archive at http://tbbeta.thebat.dutaint.com
To send a message to the list moderation team double-click HERE:
   <mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBBETA, double-click HERE:
   <mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------


You are subscribed as : [email protected]


Reply via email to