Easily user adaptable time schedules

[Robbert Mak]

Hi Guys.

Question regarding the time trigger and the time condition.
We can create a time condition to start on let’s say friday 1100PM. If we do that @ 1000AM it shows the correct next trigger moment (friday 1100pm). But when I change it to also start on tuesday for example, it changes the next trigger moment to that tuesday (while it’s still friday 1000am). In my opinion the next triggermoment should be still friday 1100pm. This is very annoying, what am I doing wrong?

Thanks.

Robbert

[Christoph Paduch]

Hello Robbert

there are different mechanisms in the Time Trigger and Condition blocks of the Workflow Designer.
One schedules the next trigger action, one checks, if a condition is true at the current moment and one calculates the next valid date and time in order to visualize it. The visualization has a little issue:
When selecting more than one day of the week, it shows the wrong date for the next trigger action.
The trigger action itself will be done at the correct date and time and is not affected.
The issue is already known.

So you do nothing wrong.

---

Kind regards / Freundliche Grüße
Christoph Paduch

[Robbert Mak]

Thank you Christoph, good to know.

My client wants to be able to change the start and stop times manually thru his actionpad.
How would you approach this? At this point they are programmed in sympholight.

Can I somehow create a time input field on the action pad that they can fill in?

Robbert.

[Victor Pyatykh]

Really interesting question. Lot of clients wants to set up manually time of switch off. For example, Astrotimer starts scene at sunset, and client wants to switch off 22.00. And change this parameter manually from time to time.(depends seasons and events).

[Georgiy Nevolin]

Hi Victor.
To set the trigger response time via the web interface, you can try to use the settings from the file that is in the attachment.

Attachments:

1. Setting-the-trigger-time-via-the-web-interface.lprj

[Christoph Paduch]

Hello Robbert
Hello Victor

Currently it is not possible to access the timetrigger properties by workflow or scripting.
In the just released V3.0 Service Release 6 the preview issue is fixed.
When you just want to simply trigger on a time, you can try this workaround:

Create a Sequence, remove all tracks. Set as many trigger points as you will need, one for each time.
Start the Sequence with a ShowInitialized trigger in the workflow.
Create a Timetrigger, that will synchronize this Sequence to the running time once a day.

You can get the actual Date/Time with a GetObjectProperty Block from ShowInformation / Date/Time Property.

With the script

public static class BerechneSequencePosition
{
    public static long Run(DateTime TimeIn)
    {
      	return  (long)(TimeIn.TimeOfDay.TotalMilliseconds *1000.0);
    }
}

you can calculate the current time in µs. The returned value has to be set with a Change Object Property block as a new position of your Sequence.

Now the Sequence shows the actual time.

You can also set the positions of the Sequence Triggerpoints with Change ObjectProperty blocks. Here you will need µs, too.
Now you can just get the right trigger from the corresponding Sequence Trigger Point blocks.

In the end this is a lot of work for setting start and stop times.
And editing the time on the ActionPad is also still missing.

But I hope, I could give you an idea, how to solve this.

---

Kind regards / Freundliche Grüße
Christoph Paduch

[Robbert Mak]

Ow wow, that is a loooooot of work to get a very basic functionality working.
Can you please create an option to use an input field from actionpad (some sort of timepicker or an editable dropdown menu) to the input of the time condition block.

[Robbert Mak]

Any news on this? We really need it. Just like password protected ActionPads…

[Autor]

Beiträge