(we discussed in blender chat, summerizing here)

In T63024#706796, @William Reynish (billreynish) wrote:

Sure - let's postpose adding this to 2.81.
IMO, this should affect all selected items - if you only want to rename one item, you should just have one item selected - we do this for basically all other operators, ie delete, move, copy, paste and so on.

Would rather postpone this, there are too many unfinished projects for 2.80 no need to add more.
We're likely to rush it and do it badly if this is made a 2.80 target.

Was there any issue doing this in one operator? (it can work like the current rename operator).

We could avoid f-strings for text which needs to be translated if this complicates things too much.

They're blended at 50%, they're not %100 saturated to begin with, causing final color to be duller than it could be.

This isn't enough information.

Note that the fix doesn't support numpy, it just avoid the error.

Right, this is a problem with the script that needs to be fixed.

Note that such large exceptions aren't great and make exception handling not work well as a way of intentionally allowing for an error with a fallback action (although the use case for a try/except block here is questionable, it's not good that it can be such a bottleneck).

The add-on needs to be updated for the renamed icon, see: https://wiki.blender.org/wiki/Reference/Release_Notes/2.80/Python_API/UI_API#Renamed

The error looks to be an encoding issue with the path your loading.

Note that this was removed intentionally, the order on number keys was mapped alphabetically, would only add this back for the 2.7x keymap.

Note that this is working for me, most likely a difference in my svn checkout which holds all languages. in locale/

Adding Y & Z will require many more changes, this wouldn't be for 2.80.

In D5097#116437, @Peter Fog (tintwotin) wrote:

If my memory serves me correct, working directly on the selection was not reliable, which made me use the clipboard instead.

In T65872#702217, @William Reynish (billreynish) wrote:

I find it super confusing that we have both. It’s very unclear what happens if you enable one or the other, and it’s just generally confusing.

The issue is caused by the filename of the path being imported.

Using the clipboard for text tools is a hack which could interfear with the users workflow (they could have some rich text in the clipboard - unrelated to using Blender, which gets overwritten by using this tool).

In D5117#116398, @Brecht Van Lommel (brecht) wrote:

I think the empty space looks pretty bad. Personally I think the Windows like behavior as explained in T62309#705066 is a better solution.

Committed alternate fix rB1c94030238bb37918c4cd3256e0acb0b7099579d

This would re-introduce the issue from T60777.

Thanks, committed rB52b4afacb21a1627f09d6cc4450cc6a8fc56c96d

This isn't a regression since 2.7x, setting as TODO.

In D5117#116377, @William Reynish (billreynish) wrote:

@Campbell Barton (campbellbarton) Well, the earlier proposed enum menu solution I still think we should do, for the reasons outlined.

In D5117#116244, @William Reynish (billreynish) wrote:

While I would advocate for further improvements, this to me is already better than what we have.