Actor framework vs DQMH

[Konan__]

But if the only event that can occur among consecutives steps (each with its own event/message) is a stop and abort, would it be OK to self messaging?

Or if the system is OK with other messages that can be handled among steps, I guess it's ok to self-message the MHL

[Konan__]

---

@joerg.hampel  ha scritto:

---

@FabiolaDelaCueva wrote:

Check out tip 4 from this blog post http://delacor.com/tips-and-tricks-for-a-successful-dqmh-based-project/

It talks about how to create state machines inside a Message Handling Loop case.

---

I would prefer a helper loop to a state machine inside the MHL.

---

I dont understand from your blog post how to do that. Fork the event refnum? how do you place the node "DQMH_REG_HELPER" ? where does it come from?

EDIT : ok solved

[Konan__]

Why the disk structure of DQMH is flat?

would it be better to create some subfolders in the script?

So that I will put my events inside my folder, to distinguish from "built in" events/VIs?

[ryan_sheppard]

---

@Konan__ wrote:

Why the disk structure of DQMH is flat?

would it be better to create some subfolders in the script?

So that I will put my events inside my folder, to distinguish from "built in" events/VIs?

---

Use the Project Explorer for project organization. It's much easier to make project organization changes in the Project Explorer than on disk.

[FabiolaDelaCueva]

---

@joerg.hampel wrote:

---

@FabiolaDelaCueva wrote:

Check out tip 4 from this blog post http://delacor.com/tips-and-tricks-for-a-successful-dqmh-based-project/

It talks about how to create state machines inside a Message Handling Loop case.

---

I would prefer a helper loop to a state machine inside the MHL.

---

They each have their use.  

[FabiolaDelaCueva]

---

@Konan__ wrote:

---

---

I dont understand from your blog post how to do that. Fork the event refnum?

---

For a detailed explanation of why we should not fork the Event Registration wire, check out this post:

https://forums.ni.com/t5/Delacor-Toolkits-Discussions/Registering-to-broadcast-events-from-many-modu...

The general rule should be a Register for Events Node for each Event structure (with dynamic event terminals visible) handling events.

[joerg.hampel]

---

@Konan__ wrote:

So that I will put my events inside my folder, to distinguish from "built in" events/VIs?

---

We do exactly that and store all manually created VIs in subfolders. The default is "SubVIs", but that varies depending on the module.

Those folders are also reflected in the virtual folder structure inside the .lvlib.

[joerg.hampel]

---

@ryan_sheppard wrote:
Use the Project Explorer for project organization. It's much easier to make project organization changes in the Project Explorer than on disk.

---

It's also quite easy to move files around on disk in the Files view of the project explorer windows (actually something I learned from Fab!)

[TiTou]

---

@joerg.hampel wrote:

---

It's also quite easy to move files around on disk in the Files view of the project explorer windows (actually something I learned from Fab!)

---

You've made my day, I didn't know we could do that!

I never even suspected NI could add such a neat feature 😮

[Konan__]

---

@joerg.hampel  ha scritto:

---

@ryan_sheppard wrote:
Use the Project Explorer for project organization. It's much easier to make project organization changes in the Project Explorer than on disk.

---

It's also quite easy to move files around on disk in the Files view of the project explorer windows (actually something I learned from Fab!)

---

wtf really LOL

But you can't delete from that view... you can only explore... or move (also with drag/drop into the file system tree)