wtreppler
Ok, I stand corrected. Post workarounds all you want. I've seen them, though, and it just adds more time and work to my workflow.
There's no question that not needing to do a workaround is better than needing to do one. But as in the example
i commented on above, it there's something (audio, automation, whatever) in the hole, delete hole works properly with audio. So if that's your situation, you'll think it works fine.
Then one day it doesn't work as expected and the person has no idea why. However if they read that delete hole doesn't recognize there's something to be deleted if there's nothing to delete, then they can get on with their editing. And if they read that the real problem involves MIDI data that crosses over boundaries, then that can be helpful too.
Of course we all hope that this becomes irrelevant after ripple editing is introduced, but until it is, there are still deadlines for projects and it's better to have any solution than none at all. I realize for a lot of people here making music is a hobby, but for those who make their living from music software, knowing what doesn't work and how to get around any issues is worth its weight in gold.