LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Project explorer doesn't show callers for .rtm (run time menu) files (is this a confirmed bug?)

Maybe I was to quick to report this as a bug... I was unable to find anything related to it at my normal sources of information. Does someone has exeperience with it?

 

I have a work-around and this is included  in the description :

 

 

http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=6776 (message 25)

 

** Original post **

 

When a library (.lvlib) that contains a file with a run-time-menu (.rtm) file is removed from the project, but there is still a file that uses this .rtm file, both the .lvlib and all of it's vis and the .rtm file are displayed in the project Dependencies.

 

For the Vi's the callers can be found by 'Find->calllers'. For the .rtm file this always results in 'No items found' but the .rtm file remains in the Dependencies (as it should since it is still used).

 

Finding the .rtm file can be hard since it is only loaded at run-time and not at edit time(?). If someone encounters this issue, a working method:

- rename the rtm file (so it cannot be found)

- open the vis that you suspect are using this file AND try to edit the run-time menu. When this vi uses the run-time menu a warning will appear (cannot load rtm file, using default menu instead)

 

Kind regards,

 

Mark

 

---

25+ years long fan of LabVIEW. Move to Emerson looks to be for the better! See the last posts in subscription model thread.
0 Kudos
Message 1 of 7
(3,519 Views)

Addiational note:

 

The effect can be achieved even easier: The project explorer never shows the callers, not even for used .rtm files within a used project.

---

25+ years long fan of LabVIEW. Move to Emerson looks to be for the better! See the last posts in subscription model thread.
0 Kudos
Message 2 of 7
(3,517 Views)
And today it did show the callers for .rtm files... so clearly this is something strange. I will come back to it when I can isolate when the bug happens and how to reproduce it
---

25+ years long fan of LabVIEW. Move to Emerson looks to be for the better! See the last posts in subscription model thread.
0 Kudos
Message 3 of 7
(3,498 Views)

Dear Mr Beuvink,

 

thank you so much for your forum post.I noticed your post earlier, however I didn't had the chance to reproduce the problem. Your problem has been solved, I want to look what caused the problem. I will try to find some information and get back at you as soon as possible.

 

Best regards

Martijn S
Applications Engineer
NI Netherlands
0 Kudos
Message 4 of 7
(3,416 Views)

I was able to reproduce the bug: When the rtm file is in the project, but the vi that uses the file is not open the caller is shown. But when the vi is loaded the callers are not shown anymore.

 

When multiple vi's are using the same rtm file, only the loaded vi is removed from the callers list.

---

25+ years long fan of LabVIEW. Move to Emerson looks to be for the better! See the last posts in subscription model thread.
0 Kudos
Message 5 of 7
(3,413 Views)

Dear Mr. Beuvink,

 

thank you for your reply. It seems that a while back this problem has been reported to our R&D group. The request (CAR) has ID; 41579. There is the following statement in this CAR: the caller vi is in memory or not. When a caller vi is in memory, rtm files will currently never report the vi as a caller. This confirms the behavior you are seeing.

I'm sorry to say I don't have a solution at this moment, at this moment they are busy fixing this problem. You can look this up in future release notes by searching on the CAR ID I mentioned.

 

If you haven any questions, please don't hesitate to contact me.

 

Best regards,

Martijn S
Applications Engineer
NI Netherlands
0 Kudos
Message 6 of 7
(3,376 Views)

LV2013f2

 

Thanks a lot. i've had some menues that was pointing to a server path that no longer exists. so working with this project was a pain. after reading your posts i close the project (and labview), reopen it and start searching for missing menus.

 

now find caller works and was able to replace with default menus. thanks thanks....

-------------------------------------------------------------------------------------
CAUTION! New LabVIEW adopters -- it's too late for me, but you *can* save yourself. The new subscription policy for LabVIEW puts NI's hand in your wallet for the rest of your working life. Are you sure you're *that* dedicated to LabVIEW? (Summary of my reasons in this post, part of a voluminous thread of mostly complaints starting here).
0 Kudos
Message 7 of 7
(2,793 Views)