When you duplicate a scene, its title is empty even though duplication is often intended to create a variant of the scene, so the title could be similar. This forces you to copy the title and paste it afterwards, so it would be more convenient if the title were pre-filled with « Copy of [original scene title] ».
I’m copying Pierre-Gilles’s reaction:
The problem with that is the title then becomes the ‹ selector › (the scene’s unique identifier), and so you’ll end up with scenes called ‹ copie-de-detection-mouvement-entree ›, instead of your scene’s proper name. Note that the selector is immutable.
It’s a choice — you could decide you don’t care about the selector, but it then creates small points of frustration. For example, if you use the Gladys API to trigger scenes, when identifying your scene you’ll have that title which doesn’t match the scene’s current name.
Now, which point of frustration is stronger?
And
Good point. I myself often copy / paste the title to change a small part afterwards.
@StephaneB I know human nature well: if the title is pre-filled, 99% of users will click “Duplicate” without changing anything, thinking “I’ll change it later” 
Result: we end up with a multitude of selectors that do not match the title.
So my question: what’s the lesser evil?
Personally, I prefer to do my own copy/paste if I need to reuse the same name and add something extra, it avoids clicking around and not understanding what’s going on (but that’s how I work).
1 Like
That’s what Windows does, duplicating a file will by default show myfile(copy).txt.
I’m not shocked by any of the behaviors. That doesn’t help the thinking, sorry 
When I happen to get a scene’s name wrong, and if I really want the selector to be clean, I simply duplicate the scene, give it a proper name, and then delete the scene that had the wrong name.
So in my opinion, whoever wants clean selectors will be careful to modify the « copy of [name of the duplicated scene] » or will fix it with the technique I just described, and whoever doesn’t care about selectors won’t be bothered that it keeps a « copy of … »
So I prefer the lesser evil: « prefilled duplicated scene name, even if the selector ends up being copy_of_… if I confirmed the name too quickly »
2 Likes
Ok @StephaneB, I’m convinced 
2 Likes
Fixed here:
1 Like
Fixed in Gladys Assistant 4.53.0 :