On Fri, 2003-03-14 at 03:37, John Levon wrote: > On Fri, Mar 14, 2003 at 03:28:18AM +1030, Darren Freeman wrote: > > > well it does that now as soon as you leave the empty paragraph, but I > > agree that I should be able to move away and do a copy before pasting > > into the blank paragraph.. > > > I agree with that behaviour in principle, but I still like the way empty > > garbage disappears immediately. > > You can't have your cake and eat it too.
I eat cake all the time ;) It will take some clever new idea to solve the problem, but it isn't impossible. Just some way of letting LyX and the user agree about which paragraphs are temporary and should be left alone, and which ones are done and should be magically altered. Perhaps what we should do is hold off on cropping an empty paragraph until the user makes another typing edit somewhere else. That way the cursor can go where it likes, but if the user doesn't come back to the paragraph it goes away. I can handle not making an edit until I come back to the new paragraph. If I forget that, I need to recreate the new paragraph. But then I might just as well forget to add what I was going to add anyway, so it might just as well get cropped at that point. > > How about the ability to spawn a second cursor for the purpose of > > Urrgggh no. If this was a BBC B+ and it was 1984, maybe. sorry the comment is lost on me, I'm too young ;) but what about the delayed paste idea? user hits "delayed paste" which is bound to a key similar to regular paste. status bar highlights the new mode. user hits copy somewhere else, and immediately the paste occurs where the first step was performed, and the user is sent to that spot. using delayed paste also prevents the paragraph from cropping. if the user makes an edit, delayed paste mode silently exits and the status bar returns to normal. the paragraph is cropped if necessary. > > yeah well they need to read the manual ;) the LyX manual is actually > > helpful IMHO... > > Users don't read manuals but in this case they have no choice, as our > methodology is likely to clash head on with the user's previous > experience, and we do not call that a bug (and it is not a bug). there comes a point where excessive hand-holding is no benefit, and people have to use their brains. I told my father the other day to press space, he typed s-p-a-c-e to which I slapped my forehead ;) if somebody doesn't get it, they need to take time out with the manual, it's part of learning.. a little OT of course =) > john Darren
