You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using notifications, you cannot use boolean types: 'true' or 'false'
If emitted type of the notification does not match the type of expected value of the notification in a report, the error message is NOT helpful. The following example expects an unsigned long, but if the notification is an unsigned int, the error message just says, "cannot find the notification"
trigger:
whenever: notif.rob_start_inst == 1
Be great to create multiple reports for every trigger hit. In other words, create report1.out when the trigger is hit the first time, report2.out when hit the second time, etc
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Been chatting about making a v3 of MAP that addresses lots of annoyances/issues/missing features of the framework.
Enhancements
Bug Fixes
Reports
unsigned long
, but if the notification is anunsigned int
, the error message just says, "cannot find the notification"Beta Was this translation helpful? Give feedback.
All reactions