Issue when creating private event

[hutchforth]

Hi all, 

I've encountered something like this issue before, though hadn't properly characterized it. Posting here in case it is something anyone else has had to deal with / knows a solution.

When trying to create a new private event with no arguments, I get an error and the action does not complete, and leaves an empty new event case. It might be worth noting that I had previously created a private event on this module without issue, and it seems I can create a private event on any other DQMH module in my project without issue. 

In addition to not completing, the event of one of my existing event cases for a different request has been overwritten to use the newly created event...  (The event I'm creating is called "Auto Start", the event that got its event case messed with was called "Set Output"

If I revert changes via git to cleanup the partially created files and make it a public request instead, I have no issues at all. This is somewhat anecdotal but I think when encountering this issue in the past it has always been when trying to create private events. 

Any thoughts much appreciated, let me know if I can provide any additional information. 

H

[Darren]

This has been reported to the DQMH Consortium as Issue #935. It is likely happening because you have wired multiple items to the Register For Events node for the Helper Loop. Can you confirm that you have multiple sources wired to the helper loop Register For Events node other than the module's Request events cluster?

[hutchforth]

Hi Darren, 

I'm afraid that so far I have had no instance where I have wired additional sources to the helper loops Register For Events node in any module within this project, so I assume there must be some other cause. 

Best regards,

H

[Darren]

Is your helper loop a Timed Loop? Because that's definitely not a configuration that was tested or considered supported by DQMH scripting.

[hutchforth]

The timed loop came after, and I have experienced the issue previously in other modules without the timed loop. 

I'll see if reverting to a regular loop in this instance makes any difference to confirm though.

[Darren]

If you can reproduce it without the Timed Loop, and if you're able to share a project with me (through a forum DM), that would help the DQMH Consortium with investigating the issue.

[hutchforth]

Also not sure if its worth highlighting, the event being created is handled in the main MHL, not the helper loop. 

While this is in my screenshots I didn't state it explicitly. 

[hutchforth]

Not sure what changed but I was able to create a private event when I tried to replicate just now in the following cases:

• Created a private request "Auto" handled by the MHL with a regular loop as the helper loop
• Created a private request "Auto" handled by the MHL with a timed loop as the helper loop

I've been doing other work since this last occurred so I'm not sure at what point in my repo the problem originally occurred. If it occurs again going forward I will keep track of the actual commit so hopefully I can replicate more easily. 

Apologies for the lack of extra info for the time being, I will update this thread again if I am able to gather more comprehensive info / steps for replication.