There should be better indicators for why Ripple Delete is not possible

[efficient_person1243]

To play whack-a-mole with your timeline to find why a certain track is unable to be ripple deleted is insanity-inducing. The sync-locks on this sidebar should be highlighted or maybe not highlighted if you try to ripple delete. There should be better indicators for why a simple command is not functioning.

My use case is cutting out dead spots in vocal audio to align with clips and stay independent of the backing song track. To accomplish this I need to continually variably trim, select, slide, etc., ad nauseum just to slide a track left. Come on you guys!! Please!! So many instances of this app are completely devoid of situational context clues about its workflow and hardstops! Come on! My entire past month in this forum is constantly ringing the bell for new ones that fail to be noticed or changed that would benefit everybody.

[MyerPj]

Oh, no! Once again PP is missing the kind of message you want. 

https://community.adobe.com/t5/premiere-pro-ideas/add-more-information-for-users-to-define-what-need...

Some messages are more informative than others. PP is not exactly easy to learn.

Why have you toggled of sync-lock? Maybe it is locking the tracks that you need to do. 

If you think the app messages are so inadequate you might consider writing your own.

[efficient_person1243]

Sync lock toggled off allowed ripple delete to function once whack-a-mole was conducted on the various tracks. A better visual indicator would be more useful, like highlighting the track preventing ripple delete in the first place. PP understands there is a track disabling ripple delete, PP understands various functions and inboard code that prevents functions but does not state to the end user why that is. This is poor design with negative user experiences.