Custom run-time menu missing in built executable

[Synaesthete]

I've created a custom run-time menu for a tree control in LabVIEW 10SP1.  This run-time menu appears in run-time and works fine.  I have included the .RTM file in my project.  In the built executable however, the custom run time menu does not appear when right-clicking the control.  What is the correct procedure for including a custom run time menu in a built executable?

[falkpl]

If I remember correctly there is an issue where the menu only works correctly if you use the save with control option, otherwise it dissaperas when in the executable.  There are some posts on this but they are hard to find.

[Mads]

And this is still the case in 2012 SP1...Will it ever be fixed? I have not checked 2013 on this yet...

[horalek]

The similar problem still in the version 2014 SP1. The executable works correct only when it is placed in original built path. It does not work after moving into another location. So it is now much harder to identify the problem... It works correct when menu is embedded in the control (tree in my case) instead of using .rtm file.

[Sam_Sharp]

I think if you set the .RTM file to 'always include' in the build specification, it might then work.

[horalek]

Thanks, I set 'always include' for appropriate .rtm file in the build specification and it works fine. Good to know it!

[Mads]

---

@Sam_Sharp wrote:

I think if you set the .RTM file to 'always include' in the build specification, it might then work.

---

That was not true before...but I see that it is now in 2015. I had to retest it here now just to make sure, because I was quite sure it was not like that before...

So they have done a change in 2015 I think, but have not made it detect the link automatically (you still have to tell the builder that it needs to be included).

[Sam_Sharp]

I'm pretty sure it also works in LV2013 - I have an application at the moment which uses a run-time menu file and it's included as 'always included' in the build specification so it shows up in my application.

[Mads]

I think the reason why you get things to work is that you are testing on statically called VIs only. There has been an improvement with regards to dynamically called VIs in 2015, but the fact that you have to manually tell LabVIEW that the menu is associated and should therefor be included in the build is still there:

here is an overview of the working and not working scenarios from 2012 to 2015: