Francois Normandin Posted January 26, 2020 Report Share Posted January 26, 2020 This bug affects VIPM 2019 (not tested with earlier versions). Problem: The .mnu file located inside a library does not relink when building the library into a package. How to reproduce: In Caraya.lvlib, there is an "Application Menu.rtm" menu file that defines the menu for the interactive UI of the Basic Test Manager class. After building the package, the menu file's URL does not relink properly in Caraya.lvlib. Before build (from source Caraya.lvlib): After installed package (from toolkit location of Caraya.lvlib): Current Workaround: Extract rtm file from library. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 26, 2020 Report Share Posted January 26, 2020 Thanks for posting this, @Francois Normandin. I'm happy to help debug/fix this. Quote Link to comment Share on other sites More sharing options...
Jim Kring Posted January 26, 2020 Report Share Posted January 26, 2020 @Francois Normandin Can you create a very simple VI Package project that has an LVLIB with an RTM that reproduces this issue? This will simplify the debugging. Quote Link to comment Share on other sites More sharing options...
Francois Normandin Posted January 26, 2020 Author Report Share Posted January 26, 2020 Sure. Here is a sample project with LV2013 SP1 and a build deployed in LV2017 reproduces the issue. The package installs the example under "vi.lib/testing" folder. testing_lib_rtm_bugtest-1.0.0.1.vipVIPM RTM LVLIB Bug.zip Quote Link to comment Share on other sites More sharing options...
Colbrunn Posted February 14, 2023 Report Share Posted February 14, 2023 Did this ever get resolved? I am experiencing this now. I have tried it with VIPM 2021.0 build 2750 and 2754. We have not seen this before. I looked through the VIPM release notes I could not find this fix mentioned. Quote Link to comment Share on other sites More sharing options...
Colbrunn Posted February 24, 2023 Report Share Posted February 24, 2023 To add more data to this. Not only does the path to the .rtm get messed up in the library, but it also gets messed up in the vi/control itself. The path that it is looking for the .rtm file is in the temporary folder that VIPM uses when it builds the package. For example: (C:\Workspace\.Package) where the Package folder has the period after it. So, it seems to me that when VIPM does the install and then LabVIEW compiles everything, the rtm file paths are not re-referenced as part of that recompile process. Our work around was to save the menu with the control itself and not as a separate file. This is fine if the menu is only used in one location. It is a pain if it is used in multiple controls (which is why a .rtm file is handy). BTW we also tried with the latest VIPM package and it still has the same issue. I am wondering if this is supposed to have been addressed, or there is a plan to address? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.