On 14 Mar 2003, 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.. > > for example, with two Standard environments and a lyx-code in-between, I > want to paste in some code. I *must* paste into lyx-code, not standard, > to preserve formatting. but as soon as I wander off the lyx-code > paragraph is gone and I have to make it again.
I think the real question here is why the user, we (or some of us at least) feel this need to create an empty paragraph before we paste? Is it that we're not sure where the paste will end up or something else? Any psychologists here? If the reason is that we're unsure about where the pasted text will end up, maybe that can be solved in some other way? I tried pasting (to see how I would behave) using Alfredo's horizontal cursor (the "Alfredo cursor"..., i.e. no new empty paragraph is created when you press enter.. instead the cursor becomes horizontal and goes to the beginning of the line, just before the next paragraph), Unfortunately, pasting doesn't work properly so I couldn't get a feel for it, nor see if I'd stop trying to create an empty paragraph first... > for example, with two Standard environments and a lyx-code in-between, I > want to paste in some code. I *must* paste into lyx-code, not standard, > to preserve formatting. but as soon as I wander off the lyx-code > paragraph is gone and I have to make it again. weird... for me (1.3.x-qt) it's the other way around... pressing enter in LyX code creates a new paragraph that _does not_ go away (which I often find very annoying...). > you have your regular copy and paste, plus a new "delayed paste" which > marks this spot as where the next copy is going to end up. so you > reverse the order of copy paste, and when the operation is complete you > are sent to where you just inserted the data, as if you had fumbled > around for the source data and then back to the destination to do a > paste. Having a special paste operation seems complicated (at least for explaining to newbies). What about using a timer/countdown (5-10 seconds)? I.e. the paragraph will self-destruct a certain amount of time after you leave it -- and there could be flashing countdown time showing in the empty paragraph... then the visual "shattering" that happens when the paragraph disappears could be called the "explosion" ... (this is partly a joke - I don't think the coding effort is worth it). /Christian PS. I tried backporting Alfredo's h.cursor patch, but gave up after a while. Besides me having no clue about what I was doing, it seems that the two breakParagraph()-function I found now take a 'ParagraphLists &'-argument that wasn't used in 1.3.x before. And this has changed in several places that are not a part of Alfredo's patch. DS -- Christian Ridderström http://www.md.kth.se/~chr