I want to compliment aberfoyle for the assiduity and patience to write down all the li'l stuff. A software growing so fast as Locus needs some reflection on the details sometimes. Thanx for that. And i can confirm most of the items in his list.
The problem with long names in tracklist exists for one year.
@aberfoyle: uff, you probably not yet know, that I don't like too long posts 
...
3) I do not consider this to be a problem. Make your names shorter and another important information place into description (that should be also visible in list. At least part of it)
...
As you can see in this
thread, menion promised to keep this in mind. So i'm waiting patiently.
Due to this problem I changed some times ago the syntax of the naming and renamed and shortened all my tracks in DB and on PC also - a lot of work. Now with version 3.3.0 i have 38 characters in one line on Galaxy Note instead of 33 before (smaller font size in list??) but most of the long names are still cutted. With 3.3.0 there is a small teaser from description visible in tracklist. Thats great and a little help! So i have to change all of the description to use this as a workaround for the missed second line.
But with this feature showing also the map thumbnail and some values (height meters are missed!) the list is tattered and tracks are difficult to find when a lot of tracks in the list. And i have a lot of tracks.
So i suggest to solve this new (small) problem and keep the tracklist scalable make a foldable container wich is closed by default and can be opened by tapping on the track name. This container can contain all the preview and values and the teaser of the description and other stuff still to come. The list is going to be a list again.
I guess new problems are generated when Locus is pimped by mini maps, thumbnails and more information because the area which can be used has still the same size. So be careful when pimping

I'm old school: expecting compressed information, no trumpery, K.I.S.S.
So i'm a little bit afraid that Locus can become ... to big and multicolored. May be the young dudes expect it. Me not.
Functionality has the priority. And no software should force the user to do something he doesn't want.
Regards,
Christian