Crossfade twilight zone

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!

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.

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.

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.

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.

Funny you should mention that about the manual tool switch. I've never used the individual tools, I always grab the multi-thing cause it always works (until now). I just tried using the one that has the wrench icon and it worked....weird..

The Smart Tool is great for when you are flying around doing various tasks but I find it much easier to toggle to the dedicated tools if I'm going to be doing a lot of something and don't want to worry about hotspots or if the ST is giving me a hard time. I mostly toggle between the Smart Tool and the Move Tool. Remember too that if you right click on certain tools in the HUD some of them have different modes as well (meaning they turn into completely different tools). Many of those hidden functions are extremely useful or sometimes the ONLY way to perform certain tasks. Even if you don't end up using them the Tools entries in the user manual are very eye opening.
 
Cheers.

Thanks everyone!