It would be useful for Trigger Flow Touch Action would include a Argument

My use-case would be: I have some semi complex formula that creates a month’s days colored, highlights holidays and flagdays… it uses si(mindex) to choose which month to show (0 is current_month)

now, I wish to add a open/collapsed state for these where I can click a month and it would show only that month and each event in that month (in text).


adding these into Komponents, and using flows/touch in those ‘works’ but is unreliable due to what I think is loading messing with si(mindex) results.

so, I would want to get the index of the clicked object, in this case it’s a text-object.

I figure the easiest way would be for the Manual Trigger in Flow to set a local variable #arg or similar that would be fetched from an extra field in Touch Action Trigger Flow, allowing for formula usage in that field to solve $si(mindex)$ or whatever else

2 Likes

Ok got it, so you want to pass a value to the trigger, the trigger will then basically set a local variable to a given value, so you can trigger a flow with an initial value, this is a good idea, let me see what i can do

1 Like

Hi Frank,

How about an action triggering another trigger (a nested trigger)?

Thanks.

yea, that’s essentially it.

I would like for the value to be evaluated on each trigger, so that $si(mindex)$ would send it’s value and not it’s formulae

You can already do this by changing a global and triggering a flow on a global change

The new beta has this available (its being released now), basically you can pass an argument to the trigger in the touch action, that argument will be available both as $lv(last) and $lv(trigger) local variables, so you can pass mindex if you want

2 Likes

This topic was automatically closed 25 days after the last reply. New replies are no longer allowed.