Project clone, global scope ...

Skip to first unread message

Jun 18, 2022, 9:21:31 PM (6 days ago) Jun 18
to Tasker
Is there any way yet to clone a project and avoid naming conflicts of profiles, tasks, and variables?

Might there be an existing script which will open, modify, and save an exported project so that it can be imported without conflict?

Or can we define here some patterns that code would follow to make that happen? Like, open the XML, get all nodes named Foo and add something to the end of the node values to make them unique...

Is there yet any way to isolate a project so that its components don't have global scope? We value the idea that assets can be accessed across projects ... but sometimes not.

If this isn't in there yet, what's the thinking that has prevented its development?

Reply all
Reply to author
0 new messages