What did I screw up now? I've never had this issue before. I'm working on a track with multiple take lanes. I want lane 1 to overlap lane 2. No dice. As soon as a grab the edge of one lane, the dreaded crossfade cursor appears and the other edge moves over to accommodate the space I just trimmed. NO, not what I want. I checked all the options SOS, crossfade is turned off, but I can't stop Sonar from doing it. What magic switch do I have to turn on to stop this? Thanks for your help!

There are multiple hotspots on the clip edge, the crossfade is near the bottom moving up the edge will change to the slip edit hotspot with the fade at the very top.

Nope doesn't work. I always get the crossfade cursor no matter where I slide my mouse up and down the clip. The weird thing is I have a similar track below that track with take lanes and it behaves normally.

I've had issues where the Smart Tool cursor doesn't change when hovering over specific hotspots as it should but will still perform the correct function. I found making a little section on my cheat sheet of each area of the clip edge (as well as within the clip) does what is useful. Also when having a hard time dragging out the take lanes vertical is obviously helpful. If all else fails I'll just switch tools and do what I need to. I think in your case the Move tool will move the edge without having to worry about that mayhem. Not sure though because I haven't been editing for a while and I'm not booted up.
 
Cheers.

Oh and it makes a difference on which side of the clip boundary you are on. Slightly inside the clip edge vs. just outside it will do different stuff. Try moving the cursor slightly outside the clip edge and try. The amount of hotspots is really pretty crazy but after I got used to it it's pretty cool being able to do so many things.

Yeah, this is the first time I've had this issue and ONLY on this particular track. I expand the edge of a clip in one lane and the clip in the other lane shrinks and visa versa. In desperation, I just duplicated the track and separated the overlapping clips to separate tracks, but I shouldn't have to do that. And why isn't a similar track just below it behaving the same way? SOMETHING is different on the problem track, it's just figuring out what....

Well in certain cases that is considered "desired behavior" and I can't for the life of me remember/imagine the scenario you are describing but I have had to wrestle with it myself (and it ended up making sense after studying up on the Comping mode) HOWEVER if you are experiencing different behavior while perform the EXACT same moves in another track then perhaps there is a bit of project corruption occurring.
 
It seems like you have already found a workaround for this particular problem but if not try out the different tools and now I'm going to say even switch to Sound On Sound mode temporarily to stretch the track out.
 
I will say though that it sounds like you have simply been dragging the wrong part of the clip. Dragging the top middle three quarters of the clip edge vs. the bottom half of the clip edge will either a) crop all other clips in that area along with your crop move or b) leave the other clips alone and allow you to crop the clip by itself.
 
Sorry... I forget which does which and that may have been confusing but either you are dragging the wrong section or the program is registering your drag move as being applied in the wrong area. No way to know without getting my hands on your mouse and doing it myself.
 
Cheers.

Doesn't matter where I drag, one clip expands the other one shrinks. ONLY on this track. I think you're right there must be gremlins in this particular project. You would think there must be some variable available to stop this behavior, but I sure can't find it.
 

Well there may be some specific setting on that track causing it to behave that way but someone smarter than I would have diagnose it... but yeah... sometimes it's just gremlins. I personally have experienced FAR less odd behavior while editing since upgrading from X2 but the stuck cursor mode thing has still been an issue. Fortunately for me it mostly seems to just be a graphical thing (maybe my vid card is being weird).
 
So this problem persists on your new track as well? Maybe if you describe the track (ie: what it is, what effects/synths are used, what mode it was recorded in and/or anything else you can think of that may distinguish it) then someone else can help diagnose the issue better than I have.
 
Cheers.

And just for my own insatiable curiosity what happens if you use a different tool or switch to Sound On Sound mode? As I said I find when I hit a wall with Comping/Smart Tool weirdness I can usually workaround the problem by changing those options.
 
Cheers.