Rename option for stopwatches

[420]

Very straight forward request, i am not sure why this isn't an option already? it would be pretty usefull!

 

[Fabian42]

There was a similar thread about this here before and it basically came down to the effort of implementing. MacroDroid would have to find and update every stopwatch start/stop/reset action, every stopwatch constraint, every stopwatch trigger (and maybe even re-schedule alarms), every stopwatch text component and who knows what else.
Supposedly not many people ever needed this feature so far. I don't have any statistics on that.

 

[420]

There was a similar thread about this here before and it basically came down to the effort of implementing. MacroDroid would have to find and update every stopwatch start/stop/reset action, every stopwatch constraint, every stopwatch trigger (and maybe even re-schedule alarms), every stopwatch text component and who knows what else.
Supposedly not many people ever needed this feature so far. I don't have any statistics on that.

Appreciate the feedback!

Yes it would be some work to implement, but if i am not mistaken, once it is done it's done, right? (same as with the variables, we can rename those and it automatically changes everywhere)

There probably are not many people that "need" this option, but the "few" that do now have to delete the stopwatch and manually find and update every stopwatch action/constraint/trigger and also the actions that write that old stopwatch to a variable/log/file, it would be alot user friendly if we could just rename them!

Also there may only be a "few" people that would actually use this, but those few will add up to thousands of people over time.

I am not a developer, so i really don't know how hard/time consuming it would be to implement and if it is worth it or not.

 

[Pseudocyclic]

There was a similar thread about this here before and it basically came down to the effort of implementing. MacroDroid would have to find and update every stopwatch start/stop/reset action, every stopwatch constraint, every stopwatch trigger (and maybe even re-schedule alarms), every stopwatch text component and who knows what else.
Supposedly not many people ever needed this feature so far. I don't have any statistics on that.

That may be correct but I would be surprised if it is, I would have thought stopwatch names are user-friendly alaises of however they are identified internally by the MacroDroid app.

 

[Fabian42]

That may be correct but I would be surprised if it is, I would have thought stopwatch names are user-friendly alaises of however they are identified internally by the MacroDroid app.

You can definitely export macros as XML and that contains the actual variable names, maybe they're stored like that internally, too.