Le 1 mars 06, à 22:40, Tom Benson a écrit :

With a little more effort (trapping in mousedown etc.) you can stop the row from getting focus etc.

More than a little effort, in my opinion.
You're a god if you can prevent the target row to be selected from inside the keydown event (you have to know the behaviour of the OS for every dead key; e.g shift-up arrow on Mac extends the selection by including the row above the selected one; What does contol-command-up arrow do in an OS can do something else in another, but you don't know how the target OS behave before you actually allow the key to process the selection). I think it's not reliable, RB should allow a row to be disabled (this is a standard OS property, isn't it?).
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to