Priority of task.

[Gilbert Baron]

I have a profile that turns off all sound at 2000 and then goes inactive at 0600. I assume this automatically spans midnight. Is that correct?

I assume that when 0600 arrives that sound settings go back to normal. By that I mean whatever they were wen it became active.

 

The problem is that I have to do a repeat every 5 minutes to be sure it stays silent all night because if I do not and I turn it on by for instance turning the phone from face down to face up (I have a profile that silences on face down.) and then do not turn it face down again the silence is now broken for good.

 

Is there a way to give priority to a profile Can I say that the actions of the Timed tasks profile take precedence over another (preferably labeled) profile

Furthermore I want the thing that happens at the end NOT to depend on the state at the beginning of action. In other words the profile that turns sound off from 2000-0600 should go back to on NO MATTER WHAT state the sound was in when it became active.

As it is now I have another timed profile that ALWAYS turns the phone sound on at 0605 just to be sure it is on rather than depending on a single profile to turn off at 2000 and back on at 0600

 

.

[Dave Fisher]

Easiest way is to use variables and single "set" tasks to do as you like.

In the tasks, for example "VolumeControl", you create a load of If statements. The order of these will be your priority. For example:

If %NIGHTTIME = True

  Alarm Volume = 0

  Notification Volume = 0

  Ringer Volume = 0

  Silent Mode = On

  etc

  Stop

End If

When the over night profile is active, you will set %NIGHTTIME to True, then call VolumeControl which will do the work. So, its now night time and you flip the phone. This profile will then set %FLIPPED to True, then call VolumeControl. If you wish this to override the volumes during the night, you would add the following ABOVE the NIGHTTIME entry in the VolumeControl task, eg:

If %FLIPPED = True

  Alarm Volume ...

  etc

  Stop

End If

If %NIGHTTIME = True

  Alarm Volume = 0

  Notification Volume = 0

  Ringer Volume = 0

  Silent Mode = On

  etc

  Stop

End If

So in this case, even if its night, the volumes will be set to whatever you want. When you flip if back down, you'd set FLIPPED to False, and call VolumeControl in the Exit task. This time the "If %FLIPPED" would be skipped (as its False), but as %NIGHTTIME is still True, the volumes will be made silent again.

On the other hand, if you never want sound over night, make sure its always the top statement in VolumeControl - then it will always be executed first, and the task aborted at the Stop, hence keeping everything quiet.

Lastly, set the Exit task of the Night profile to set %NIGHTTIME to False, and then to call VolumeControl. After all the other If statements, add your default volume settings. When the Night profile exits at 0600 and calls VolumeControl, as all the other If statements will evaluate to false, they will all be skipped and the entries at the very end will be executed, therefore setting the volumes to your "defaults":

If %FLIPPED = True

  Alarm Volume ...

  etc

  Stop

End If

If %NIGHTTIME = True

  Alarm Volume = 0

  Notification Volume = 0

  Ringer Volume = 0

  Silent Mode = On

  etc

  Stop

End If

Alarm Volume = 6

Notification Volume = 7

Ringer Volume = 5

Silent Mode = Off

etc

etc

Using variables and single "set" tasks is a very powerful and flexible way of getting Tasker to do exactly what you want, when you want it.

I use setVolume, setDisplay etc etc to do this kind of things. It was a bit confusing to begin with, but easier once you get going.

Hope that helps,

[Gil Baron W0MN]

Ok, thanks. So basically we have a programming language here, not just a bunch of predefined operations. Neat but this App is way beyond the average cell phone user I fear. 

I just got it and should have read more documents and examples it seems. :-)

iPad Gil W0MN

Hierro Candente Batir de Repente

[baudi]

Take a look at this.

http://www.pocketables.com/tag/beginners-guide-to-tasker 

[RudeboyX]

I personally think Tasker is perfect for all users.

for a "simple" user, you make simple tasks and use it as a simple scheduler etc.
or
for the advanced user, you can create powerfull tasks, scenes, apps etc.

Tasker is for everyone, not just programmers. and most people find themselves progressing from the "simple" user to the "advanced" user purley from playing around and experimenting.

I'm no programmer but i've adopted the tasker way. I came from simple volume changing tasks, now i've got some complex variable calculating task and widgets/scenes/scripts etc that are all very profesional looking and stable, all created with the simple UI that is tasker.

Keep playing, i'm sure you'll end up in the "advanced" user category soon enough.

RBX

[Gil Baron W0MN EVO]

Probably right but after
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.