Bug report 4.7u1m

[Morgan Young]

Using tasker 4.7u1m and a galaxy G6, tasker does not pick up on contexts/calendar entries that last over midnight, but less than 24 hours. I had one context it met that was 24 hours, but not a context that lasted 18 hours.

[Pent]

Using tasker 4.7u1m and a galaxy G6, tasker does not pick up on contexts/calendar entries that last over midnight, but less than 24 hours.  I had one context it met that was 24 hours, but not a context that lasted 18 hours.

I havn't changed anything with calendar and it seems to work fine on my N5.

Perhaps you have other conditions on the profile or the task didn't run etc, please check the Run Log.

Pent

[Rich D]

> Using tasker 4.7u1m and a galaxy G6, tasker does not pick up on contexts/calendar entries that last over midnight, but less than 24 hours.  I had one context it met that was 24 hours, but not a context that lasted 18 hours.
>

It does not sound like this is the issue however, be aware that tasker will "not" detect a calendar event that has been set by taskers 'calendar insert' action if it contains the 'all day' flag set.   It will show in the calendar but for some reason will not be detected with a calendar context.  If you set a event manually with a all day flag it will be detected.   

[Morgan Young]

the event in question ran from noon one day till 0800 the next day.  The only condition was that the word Guppies be in the title.  How I have this condition set is *guppies*  this is the only condition.
Changing the event to 1200 to 2355 caused the condition to be met.  I duplicated that event, then changed the start time to 0000 till 0800. the profile is still active now, as it should be.

Here is the profile.
Profile: Dad (14)
Enforce: no
State: Calendar Entry [ Title:guppies* Location:* Description:* Available:Any Calendar:Google:Morgan Young ]
Enter: Dad on (28)
A1: Variable Set [ Name:%Daddy To:1 Do Maths:Off Append:Off ]
A2: AlarmPad get variables [ Configuration:AlarmPad get variables: Next occurring alarm Package:com.mindmeapp.alarmpad Name:AlarmPad get variables Timeout (Seconds):2116 ]
A3: AlarmPad run action [ Configuration:Enable: 2 alarms selected Package:com.mindmeapp.alarmpad Name:AlarmPad run action Timeout (Seconds):0 ] If [ %DAYW ~ Monday | %DAYW ~ Tuesday | %DAYW ~ Wednesday | %DAYW ~ Thursday | %DAYW ~ Friday ]

Exit: Dad off (52)
A1: Variable Set [ Name:%Daddy To:0 Do Maths:Off Append:Off ]
A2: AlarmPad get variables [ Configuration:AlarmPad get variables: Next occurring alarm Package:com.mindmeapp.alarmpad Name:AlarmPad get variables Timeout (Seconds):2116 ]
A3: AlarmPad run action [ Configuration:Disable: 2 alarms selected Package:com.mindmeapp.alarmpad Name:AlarmPad run action Timeout (Seconds):0 ]

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/WUv1aprzo9I/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.
Visit this group at http://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Morgan Young]

That is interesting, but not the case here. 

On Jun 18, 2015 4:44 AM, "Rich D" <ricp...@gmail.com> wrote:

> Using tasker 4.7u1m and a galaxy G6, tasker does not pick up on contexts/calendar entries that last over midnight, but less than 24 hours.  I had one context it met that was 24 hours, but not a context that lasted 18 hours.
>
It does not sound like this is the issue however, be aware that tasker will "not" detect a calendar event that has been set by taskers 'calendar insert' action if it contains the 'all day' flag set.   It will show in the calendar but for some reason will not be detected with a calendar context.  If you set a event manually with a all day flag it will be detected.   

--