An alternative feature that would solve the same problem (and might also be helpful elswehere) is to be able to extract the changes of a changeset to a shelf.
So before deleting a changeset, you could create a shelf for all its changes. Then delete the changeset (which resets you to its parent, if it was your home), and then simply apply the shelf.
Note that you would not have to do an exhaustive search for all changed items, as with the Pending Changes view.
The dashed home is just a marker telling you "yes, something is locally going on", so it's not relevant WHAT has been changed. Therefore you could break off the search for locally changed items as soon as you find any one, speeding up the Branch Explorer refresh.
@Codice Software: As you already included the (optional) auto-refresh for the Pending Changes view, there is now an inconsistency, where the Pending Changes automatically refresh, but the Branch Explorer does not. This is very confusing and leads to mistakes.
Yep, they are only marginally useful if they are gone the next time you open the client.
But they would become REALLY useful if you can continue the next day where you left off.
NOTE this is not about labels - bookmarks are great for temprarily (and locally!) tagging certain changesets in individual workspaces, while labels are global.
We like to use labels for a lot of things ("ready for integration", "merged but task still open", "needs upstream cherrypick", "is internal baseline", "is customer release", ...). But without label colors these disctinctions are of little use in the branch explorer, as you'd have to click on each label (or try to read the lightgrey-on-white labeltext which is cut of after like 10 characters).
Marking labels with prefixes is therefore also not an option/solution, due to the length limit and light grey color.
He means the branch explorer, yes.
He means the label text itself, which is an unreadable light-grey-on-white.
What is also an idea is to adjust the color of the actual label, see here: https://plasticscm.uservoice.com/forums/15467-general/suggestions/3584266-allow-setting-a-color-for-each-label-changeset-an
As others mentioned, it is already implemented in the 2D history view, so just enable it for the regular Branch Explorer as well. And make it a Display Option, for people who don't want them.
Re: "Problem is with big cset numbers": in the 2D history view it works fine, with enough room for at least 5digit numbers