another problem with the "respond to action" model

Mahogany now has an option to do something,
like move to the next message, after an
"action".

I like the idea of conditioning on actions,
but I think actions need to be broken into
types.

I already mentioned that that the desired
behavior after deleting or moving a msg
is likely to be different that after
printing a msg.  The same is true I think
if we save a message to file: I do not
expect and do not want to move to the next
message in response to that.

I see two possibilities.
i. there are a small number of classes of "actions"
and most people can agree on the proper response.
E.g., delete should always cause a move to the
next msg, but printing should never cause such
a move.
ii. Preferences really differ across all actions,
so we need to be able to access a check-box menu
which determines the "respond to action" status
of each action.

fwiw,
Alan Isaac





-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click