I don't understand how you can innocently ask a question and be frustrated by the response when you have asked exactly the same question, received the same answers and made exactly the same complaints 5 years previous:

 
I wasn't frustrated at the response from people on the forum.  I appreciated it, and each time tried out people's suggestions, taking time to update the list of actions needd.  I was frustrated that Cakewalk still hasn't improved the workflow. 
 
It was interesting to re-read that old post.  I had forgotten about it.  Funny how the same comments were being made 5 years ago, not necessarily by me.   Even the comparison of clicks and links had been done before (not by me).  I must have subliminally remembered that.  Weird.
 
Anyway, the point I am trying to make is that many of the operations I am performing on a daily basis are slower for me in X1/2/3/Platinum than in 8.5.3.  For me, the difference in efficiency is not "fairly trivial".  It is consistently annoying. 
 
In 5 years, I still have not learned to adapt my habits to X1/2/3/Platinum.  People on this forum keep telling me "accept it" or "get used to it".  But, 5 years on, I still have not accepted Sonar X1/2/3/Platinum's "quirks", nor that Sonar has to continue to be less usable for me than it was was 8.5.3.  I preferred the more Windows-y 8.5.3, because it had a more efficient design (and less buggy implementation).  I would go back to it, except I am worried about compatibility with my more recently acquired plugins.  Also, I know that if I retreat to 8.5.3, I will not have any input whatsoever into the future development of Sonar.  Believe it or not, there is a chance that people at Cakewalk are reading these topics, even if they don't publicly acknowledge them.  I know my issues are probably low priority, but If I stop squeaking, the wheel will NEVER be oiled. 
 
If Cakewalk could fix the bugs, and bring back the UI efficiency and flexibility of 8.5.3, I will be happy.  And quiet. 
 
So instead of telling me to stop complaining, another strategy would be to +1 my posts, or submit similar bug reports.  Of course, that would mean admitting that Cakewalk has made some design (or implementation) mistakes, and to Cakewalk disciples, that might be a painful admission.  Sacrilegious.  It's much safer to tell me to shut up and accept the new status quo, isn't it?  Stop rocking the boat, Tripecac, no matter how right you think you are.
 
Heard it all before.  5 years' worth!  If I sound like a broken record, it is because Sonar is a broken program.  But it can be fixed.  Unlike me. :)

Like craig said inspector works better for renaming multiple clips.
From all the tips provided by users I guess you can do it prety quick. Set double click behavior to clip properties.
1.Double click the clip
2. Click on the name
3. select or Ctrl A. Enter the name
4. Click Enter. 

This is nothing big to complain but I understand if you have a project were you wanna rename every clip this will feel unwieldy. (but only coz you were doing this much easily before)
 
On the other hand I think what your are asking is also fairly simple. Like how now F2 opens The track name selected. Bakers can include a Ctrl + F2 shortcut which opens the clip properties automatically with clip name selected.

Tripecac
 *1: I know that if I retreat to 8.5.3, I will not have any input whatsoever into the future development of Sonar. 
 
*2: If Cakewalk could fix the bugs, and bring back the UI efficiency and flexibility of 8.5.3, I will be happy.  And quiet. 
 
*3: So instead of telling me to stop complaining, another strategy would be to +1 my posts, or submit similar bug reports.  Of course, that would mean admitting that Cakewalk has made some design (or implementation) mistakes, and to Cakewalk disciples, that might be a painful admission.  Sacrilegious.  It's much safer to tell me to shut up and accept the new status quo, isn't it? 
 
*4: Stop rocking the boat, Tripecac, no matter how right you think you are.
  
*4: Heard it all before.  5 years' worth!  If I sound like a broken record, it is because Sonar is a broken program. 

1. Given that you have had the same suggestions/complaints for the last 5 years, it is fairly safe to say your strategy is not working and this horse may well have bolted:)
 
2. They are not bugs. They are workflow changes that you personally do not like. It may come as a surprise to you to learn that many other people use Sonar too. If the majority of people did not like them I am sure that they would have been changed back by now. What you want is a Sonar Tripecac edition.
 
3. I would +1 your post if I agreed with it. Your ad hominem 'disciple' attack is as tedious as it is predictable.
 
4.I have no problem with rocking the boat, and am only too well aware of how right you think you are.
 
5. Sonar is 'broken' because you can't rename clips the way you would like to? I give up. Whine away:)

I've always found it a little annoying that I have to move the mouse cursor all the way to the top of the Inspector when I only want to change a clip name. Editing part of a long clip name is also not very easy (since the width of the Clip Properties Inspector isn't resizable and having to resize the separator in the middle is somewhat bothersome).
 
I should be easier, like this.
 

 
 

The issue here is no one knows what the cause and effect is of changes within SONAR. All program updates, not just SONAR's, often take "two steps forward, one step back." These decisions are made on the assumption that the majority of users will be happy about the two steps forward, and a minimal number of users will be upset by the one step back. These decisions may also be driven by programming issues that require the one step back to make the two steps forward possible. 
 
Perhaps the consolidation of editing functions within the Inspector streamlines the code to a degree that right-clicking on clips for everything from naming to timebase to color would be less efficient. I don't think a right-click operation goes away by itself, so I presume someone made a conscious decision to remove it, and they had a reason to do so.
 
I believe what the Cakewalk supporters are saying is that they trust CW's judgement in this matter, which is probably helped by the fact that these people feel that the overall workflow for the X-series programs is more streamlined. I certainly would not want to go back to 8.5 even though it had some features I liked, because on balance, I get projects done a lot faster since the X-series showed up.

I personally think it's best to offer a few different ways (ideally just two) to achieve the same result, especially when it's something very basic and frequent such as renaming clips. Offering too many different ways (to add tracks, for example) probably just makes the reference guide unnecessarily long and tires the users.

icontakt
I personally think it's best to offer a few different ways (ideally just two) to achieve the same result.

 
Understood, but again, I don't know what's going on "under the hood" that may (or may not) allow for that in this particular case.
 

Perhaps the consolidation of editing functions within the Inspector streamlines the code to a degree that right-clicking on clips for everything from naming to timebase to color would be less efficient.

 
A right click menu that allows access to all operations you would want to perform on a clip would be huge, and possibly slow, unless you could customise it.
 
Sonar 8.5.3 had a right click menu editor, where you could add top menu functions to the right click menu.  That was very cool.  I can't seem to find it in Platinum, however.  Do you know where it is?
 
Also, does anyone know if CAL can rename clips?

One point to think about is from a beginners point of view. CW was clear when they came up with X1 and the Skylight UI to enhance the new user experience and make it easier to do things as well as have better consistency throughout the program. This meant some things that had been in Sonar had to be moved. A lot of angst was seen with this situation. Many simply could not adjust. Others like myself had very little trouble understanding the new Sonar.
 
With the kind of fault finding that are a major part of your posts you lost some credibility. You might find a much better reception if it were put in the form of a feature request.
 
Although you are good at finding trivial issues that do have ways to get them done you seem never to acknowledge that the changes CW made have worked out very well for most of us.
 
Platinum is far and away more stable. It is faster to do most things in it and can do many more things. 8.5 is dead. Long live Platinum!      

Tripecac

 
If Cakewalk could fix the bugs, and bring back the UI efficiency and flexibility of 8.5.3, I will be happy.  And quiet. 
 
So instead of telling me to stop complaining, another strategy would be to +1 my posts, or submit similar bug reports.  Of course, that would mean admitting that Cakewalk has made some design (or implementation) mistakes, and to Cakewalk disciples, that might be a painful admission.  Sacrilegious.  It's much safer to tell me to shut up and accept the new status quo, isn't it?  Stop rocking the boat, Tripecac, no matter how right you think you are.
 
Heard it all before.  5 years' worth!  If I sound like a broken record, it is because Sonar is a broken program.  But it can be fixed.  Unlike me. :)

 
 
You are a broken record. Still whining about Sonar 8.5.3.
8.5.3 was good, but Platinum is better. Just get with the times. Adjust your workflow.
If not, you are condemning yourself to be miserable and keep on dreaming of the past.
 
One thing is for sure, Platinum is not a broken program.
You are a broken record.