You're a mouser?!?! 
In general, no. For example, I don't like instruction palettes where you can drag a NO contact down and place it in your rung.
Now, I try to leverage whatever a given brand editor does well and avoid what it doesn't. Like DirectSoft and DMD, RSLogix has both keyboard and mouse editing capabilities, and for me, rung entry in RSL tends to have three phases.
(1) Enter addressless monics to build the rung structure, say "BST XIC NXB XIC BND XIO OTE". RSL lets you enter monics with no addresses and builds the rung structure and leave you to fill in the addresses. This is a three-wire motor circuit. The DS/DMD equivalent would be "STR OR ANDN OUT", if I remember my DS monics correctly. Now, I do that for two reasons: AB doesn't let me draw lines and branches with Ctrl-arrow keys like DS does, and AB addresses tend to be lengthier and more complicated with more punctuation (think P3K), so for the moment I'll avoid typing the ones I can. I'm not typing "Local:7:I.Data.8" if I can get out of it.
(2) If your program is organized, consecutive rungs tend to use a lot of the same and nearby addresses. So the next step is to drag addresses needed for the new rung from adjacent rungs already entered if there are exact or even close matches. Close does count (are we going to have to change that old saying?), because AB's display format often makes it easy to change just part of the address, a bit in a word, say, which is still easier than typing the entire address from scratch.
(3) Finally, if there are still any missing or incomplete addresses, I type them in full or edit them to the correct address.
Takes a long time to describe, but it's actually the quickest AB-compatible rung entry method I've found. Though as you can see, a big part of the reason I think address dragging is such a big time saver is that AB addresses are way more time-consuming to type from scratch than C544 or V1200.