Transforming a singleton module into a clonable module?

[TiTou]

Hi all,

After refactoring a singleton module, I now realise it could become a clonable module.

It wouldn't be a huge amount of work to just create a new clonable module, duplicate a bunch of VIs, create the API requests and broadcasts and re-implement it. I think it would take about 16 hours in my case.

But I also thought there might be another way... by just changing the singleton into a clonable. Anyone has ever tried?

Is it a good idea?

Thanks in advance for any insight

[Ozfarmboy]

Hi Antoine,

For any new modules that you create, if there is a distinct possibility it would need to be cloneable in the future, then I recommend starting as a cloneable - because you can always set the Run as Singleton? to TRUE. Easy to say in hindsight though!

I think you'd be better off just creating a new cloneable module, and re-writing the module.  There are quite a few differences between a singleton and a cloneable.

Also, I raised a feature request for this idea here: https://forums.ni.com/t5/Delacor-Toolkits-Documents/DQMH-Feature-Requests/tac-p/3926171/highlight/tr... 

[TiTou]

Thank you for your answer Christopher,

---

@Ozfarmboy wrote:

For any new modules that you create, if there is a distinct possibility it would need to be cloneable in the future, then I recommend starting as a cloneable - because you can always set the Run as Singleton? to TRUE. Easy to say in hindsight though!

---

I had already received that advice, and obviously I should have followed it. I guess that's what learning by mistake is.

---

I think you'd be better off just creating a new cloneable module, and re-writing the module.  There are quite a few differences between a singleton and a cloneable.

---

I did compare clonables and singletons and yes, I guess that's what I'll do.

I've just updated my DQMH to 5.0 now is a good time to go ahead and create a clonable from scratch and re-implement.

---

Also, I raised a feature request for this idea here: https://forums.ni.com/t5/Delacor-Toolkits-Documents/DQMH-Feature-Requests/tac-p/3926171/highlight/tr... 

---

I had missed it, this thread for feature suggestions is far from ideal.

[PRNN]

I just do the same error 😥. Since 2020, have there been any improvements to solve this problem?

[joerg.hampel]

This has been requested a few times in the past (see this feature request). I'm sorry to inform you that the DQMH Consortium has no plans at this point to implement this feature, as the effort would be enormous and our resources are limited. 

However, we are considering to provide a tool that will make the migration from a singleton to a cloneable - or vice versa - easier (original description here). Basically, the tool would create a cloneable module, read all requests from the singleton and recreate the requests inside the cloneable. The user would still have to move the code from each MHL case in the singleton module to the MHL of the cloneable module.

[Ozfarmboy]

Joerg - the ability to do what you said here (via the DQMH API) is already possible in DQMH 6.1 right?  It's just there is no tool to automate it?

[joerg.hampel]

---

@Ozfarmboy wrote:

Joerg - the ability to do what you said here (via the DQMH API) is already possible in DQMH 6.1 right?  It's just there is no tool to automate it?

---

That’s correct. 

[PRNN]

Thank for the replay,

Please when will be the tools available?

[PRNN]

I don't know why but I use the DQMH version 6.0.0.83 and my VIPM dont give me a more felt version. Is the 6.1 already available for user?

[joerg.hampel]

---

@PRNN wrote:

Please when will be the tools available?

---

Although we have talked about it and appreciate that it would be useful, we don't have any concrete plans to implement this tool at the moment.