Ashley - but why would anyone need that?
I didn't provide a capx because it hinges on my explanation... Which if its supposed to work like that... but I don't understand... why would anyone need that? Its not like they couldn't just select it from the panel? And a properly optimized tilemap usually won't have a whole lot of continuity as far as tile relations go.
I've attached some gifs that illustrate the problem a little better than words can.
In this first gif, I begin by creating a slope. I want this slope to repeat for a while but there is no good way to select a larger shape, so I build it block by block for the most part.
https://www.dropbox.com/s/l1dhtl55qx9b1 ... p.gif?dl=0
The real kicker comes when I want another slope, that looks the same... or perhaps that I need to move the slope over by 2 blocks... I can't. But if shift click drag copied from the tilemap and not the source, the built in tilemap becomes... well, usable. For example:
https://www.dropbox.com/s/sgydlsj4s2b9p ... s.gif?dl=0
I remember Tokinsom having talked alot about this a while back, and I recal alot of people getting excited over simply shift right click copy, which is super handy, but its handiness exponentially grows with dragging. Being able to rotate and flip these selections is the ultimate tile mappers tool. But I know for one thing Tokinsom wanted to be able to copy from the map not the source when he mentioned drag copying...
Again... I don't understand the need to copy from the source, unless you have a rather redundant source image.