The screen shot shows how the icon half obscures the last section on the bottom of the screen. To be honest the whole placement looks a bit bodged, there is lots of space in the title bar for that icon (between the search icon and the Tasker word) Wouldn't it be a better use of space to insert the + icon there?

Another alternative then would be to place the + icon before the house icon on the bottom row with a separator between. The point being that the + icon isn't obscuring any other items or text like it

Doing so would allow conditions to be named for easy use only for Profile Active State triggers.

The current workaround it's to have such profiles associated with a "No Op" task.

Request to have also a "double tap" option (in addition to tap, long press, and stroke) in scene elements to trigger different tasks.

Input Dialogs has replaced some of my custom Scenes. However, I find it annoying that tapping accidentally outside of the dialog cancels it and defaults to a negative value. In my opinion, it would be better to make it persistent and set a timeout instead like Popup Task Buttons. Thank you.

Hey,

Would be great if a torch status profile could be added to allow actions to be triggered based on whether the torch status is on or off.

Thanks as always

The ability to import and export individual tasks and profiles using tasker actions as opposed to AutoInput or manually.

While this is do-able using AutoInput, a dedicated action would ensure reliability and remove ~20 actions from a task that I currently use to import a profile into a specific project

A tasker action could import a specified xml into a specified project. A second action could export a specified task or profile (or project?) and save to a specified location

When I first used it I thought that the time settings were a timeout not the check condition timing. Some method should be provided so that if the condition never becomes true the action can timeout with an error code.

An option in the loop (If, For) blocks to automatically display in collapsed view when editing the task. Possibly a set of dummy blocks under Misc whose only purpose is to collapse chunks of code. 

add "wake on lan" funtionality

It seems to me there's only one place where the + button function should be constantly visible - in the Task editor as another standard button, as shown...

  There's a logical / intuitive place for this function elsewhere - as a menu option on each category tab title - PROFILES, TASKS, SCENES - it's already on the Project tab.   Here's how I see it...

If you agree this format has merit, please vote by clicking the support button beside the post title. 

I just had an incredible idea that might be of interest to Tasker users, and would be of exceptional help to myself: Source control like you see in git.

Commit and Push: You could make changes to your Tasker project, commit and push those changes to a repo (say on github, or VSTS), and be able to revert those changes by reverting the commit. You'd be able to see what changed between commits.

Branches: In addition, being able to make "branches" to allow for further source control, (for testing, specific sets of features, etc). The ability to merge branches and

New search option--

  You can currently tap the triangle next to the search text box to reveal the Contains / Matches / Regex .  I propose a new category of "Tasker ID number"  This would allow to search for any id number for profiles and tasks without having to use profile or task names which can give to many results sometimes.  So searching for a task by task Id number will now show you any profile or scene that is linked to the task (very useful ) and allow you to tap the task Id number of a

The Page Load event of the webview element allow us to get the url. would be possible get the html content in a variable? This option can allow users to get html content after ajax loading in some pages.

João said the following the Tasker Google forum:

• Unfortunately when the previous developers created scenes he made it so that they couldn't show up in recents for some reason I don't know yet. I would have to figure out why that is and potentially restructure the whole scene system so that it works properly.

I have one idea of implementing this:

1) Store last scene shown.

2) Show that scene via the kid app's Persistent Notification.

3) If possible, do return to the app or that last scene via the App Recents list. This is the most stock the experience

It would be very useful to be able to use Quick Settings Actions when the device is locked. As for security concerns there could be a toggle in preferences to dis-/allow this behaviour.

Hi,

Ideas:

• an easy to use library that supports designing custom automation logic in some programming language that will run in (indirectly) or on top (directly) of Tasker
• Indirectly (main idea): using the Tasker's backup system, a support library and custom logic written in Python, should be able to output an XML that contains tasks and profiles
• Directly: same as methods under Code action but more robust, (probably using indirect technique to inject script into action)

I imagine that my whole tasker environment could be simplified to a Python project thats easier to understand, debug, maintain, comment, share and most

If tasker can host a small webserver which can host any local html files, we can expose lot of features such as toggles, scenes etc to the outside network and can create lot of cool use cases.

I'd like to be able to use a variable to identify the path to the folder I want to guard. At the moment this seems not to be possible, since if I use a variable with the name of the folder then the profile doesn't react to any event. It would be very useful!

A stopwatch as a Task.

For example in the “event” of screen turned on , We could be able to add a stopwatch task to start time counting up and outputs a variable so that we could know how much time has elapsed

I know we could do that by doing maths on TIMES var, but there are times that the stopwatch itself is needed like pausing it and resuming it and still would be able to have a variable to output the seconds or time past