Macro implementation when using triggers is not working
See original GitHub issueThis works:
discoveredDist <<= (dist in ReactiveRuntime)
.storeAs(discoveredDist in Global)
.triggeredBy(dist in ReactiveRuntime)
however this doesn’t:
discoveredDist := (dist in ReactiveRuntime)
.storeAs(discoveredDist in Global)
.triggeredBy(dist in ReactiveRuntime)
.value
Issue Analytics
- State:
- Created 9 years ago
- Comments:18 (7 by maintainers)
Top Results From Across the Web
Trouble triggering a macro when a specific cell has a specific ...
I'm new to macros and apps scripts. I have tried to implement all the suggestions from the following links without success;. How can...
Read more >Problem with Macros in TexStudio - LaTeX Stack Exchange
Triggers are inactive while the completer is active. For example you cannot trigger on \\sec if the completer is open suggesting to complete...
Read more >Update Trigger? Data Macro? Stuck in Access 2010
I have a form for people to use to update equipment parameters, such as calibration dates, verification dates, where the equipment is located, ......
Read more >Data Macro triggers/fires only under certain circumstances
I'm trying to use "data macros" as a basis for performing a trigger-like action in Access (365). Ordinarily I might do this simply...
Read more >Events trigger with no instance - ServiceNow Community
Solved: I am using a ui macro to call a script include to trigger an event to send an email. the issue I'm...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
thanks, worked fine with that version 😃
Is there a workaround to this issue that will achieve the same behavior without triggering a deprecation warning in sbt?