| Search |
|---|
| ID | Rating | Category | Description | Screenshot | Date |
|---|---|---|---|---|---|
| 5515 | 🙂 | General | A bug concerning behaviors: "Parameters are not market as input when they're passed to a subroutine that uses it as both input/output". I'll try to describe the full reproduce process for my case. I have a behavior Foreman, calling a _CheckNotifyBlight calling _NotifyThrottling. The way I have it setup is that Foreman keeps it's variable value and pass around a "state" for the underlying routines. _CheckNotifyBlight and _NotifyThrottling both take that state as first param, reading and writing into it. For _NotifyThrottling it's correctly shown in the parameter UI (both arrows) For _CheckNotifyBlight calling it though it's incorrectly marking that state param as only output (yellow up arrow). It does not seem to recognize that passing that param to a subroutine doing both input/ouput with it, should make it input/ouput for itself as well. It's not only a visual bug because _CheckNotifyBlight indeed does not use the state it's given, as it's marked only output. My working around is starting _CheckNotifyBlight routine by copying state into itself, which count as a read and marks the param as input as well, fixing the issue. I'm attaching my save it that helps! | 2025-07-21 13:13:38 |
| ID | Reply | Author | Date |
|---|