1

Export description to variable

I currently send all exported descriptions to a text editor via the clipboard. This helps with debugging and allows me to give them a final review before posting.

The issue is that this overwrites the current value of the clipboard. 

Could we add a way to export to a variable?

2 replies

So, do you mean an action in Tasker that would export the description of a task/profile to a variable?

RR

The way I had envisioned this was:

  1. An optional Tasker preference where the user could define a valid variable name.
  2. If that setting is defined, a menu option appears to Export to variable.
  3. The user then would just need to monitor for changes in that variable.

The advantage of this approach is that no new actions, contexts or global variables need to be defined.

Thanks Robert. I think I actually prefer to have an action to do that 😅 Maybe an action that has options to export either the XML, description or URI of Projects/Profiles/Tasks.

That way you can also define it in a variable and it seems cleaner to me than having a setting + menu option.

RR

I don't think you can avoid using a menu item. There has to be some outside user action that initiates the process.

What about having the menu item send an event? The event would pass two variables, one containing the description and the other containing the XML.

Only two things would need to be defined, the menu item and the event.

But if you had an action in Tasker to do it, couldn't "running the task" be the initiator?