Bo Peng wrote: >> > Logically speaking, we should saveSelection after cur has moved to its >> > place. In that case, cur is undispatched so saveSelection should not >> > be called. >> >> Maybe the best would be calling saveSelection at the end of >> Cursor::dispatch (maybe adding the check if the cursor has moved), and >> nowhere else? > > That makes sense but as I have said (or implied), to avoid > introduction of new bugs, it is unwise to overhaul clipboards now. > JMarc's two-liner stops crashes, my two-liners saves selection > correctly for that particular case. I think these are enough.
Seems fair enough ;-) A/
