Jump to content

Red X on Palette VI's


Recommended Posts

Has anyone see this and know why it occurs?

Using LV2010.

Tried the menu's in the lvlib and the lvclass.

The examples show up ok (assuming because they are outside the library).

Default palette set for the lvclass to dir.mnu.

The vi's drop out of the palette ok...they just have the X on them.

I am using the lvlib because I am giving the option to build a packed library. It is really slow and hogs a bunch of memory in the development environment though when I am working with it so I just went to a source distribution. Might try 2011 to see if they optomized it.

Thanks

post-2966-0-47292700-1314265191.jpg

post-2966-0-66226300-1314265208.jpg

Link to post

/shrug

The X marks are annoying, but as long as the palettes work I don't mind much. Odd.

Definitely not fixed though. LV2011, these are public methods of a public class in an lvlib:

post-11742-0-44700500-1314278008_thumb.p

Link to post

Thanks for the information guys. I guess I should have searched Red crosses and not Red X. It was late, sorry.

I will try it in 2011. Maybe resave all of the menu files when I do incase they fixed it in the way they are saving the menu files themselves. I'll let you know if resaving works.

Thanks again.

Link to post

By fixed, we mean the symbols showing up incorrectly. The X will still show up sometimes for correct reasons.

The X means that you do not have the license file so this VI will be broken.

I *think* it can also show up in right-click palettes when the VI you clicked on does not have access scope privileges to use the VI in the palettes. So if there's a private scope subVI in your palettes, you'll see the X when you pop up on a VI that is outside the library that owns that subVI. I say "think" because the feature was proposed that way, but I haven't kept up to know if it actually was implemented.

I can't explain why mje is still seeing a problem. Can someone post this on the ni.com forums so an AE can dig into it?

Link to post

I am going to check this out more (since I report the original issue and filed the CAR).

(Just thinking out aloud)... ...@mje, I know your code is installed in LV 2011 - but is your code compiled in LV 2011 in the images above?

Cheers

-JG

Link to post

/shrug

The X marks are annoying, but as long as the palettes work I don't mind much. Odd.

Definitely not fixed though. LV2011, these are public methods of a public class in an lvlib:

I'm not seeing the Xs:

post-17894-0-54733500-1314295221_thumb.p

I'm pretty sure the fix didn't require any action on your part. I noticed the package you attached here didn't include any palettes. I wonder what happens if you don't include the palette files. The CAR mentioned above (185059) included a palette in the example code.

Link to post

Hehe, I forgot I posted that preview. You're right, no palettes included. My current library is version 2.1 (despite that the palette says "2.0", oops file that one under "bug"). This version was compiled with 2011 as it uses the new start async call nodes. I'll get an export generated tonight and post it to see if the problem can be reproduced.

I really ought to finish that library one of these days...

Does it matter how the palettes were added to LabVIEW? All I ever do is edit the set manually via the advanced menu option and add the existing mnu file. Too busy (lazy) to create an installer for the library.

Link to post

Recompiling in 2011 worked. The only vi with a Red X now is the property node which is a broken vi because I don't have the class going into it(setup for place vi contents).

post-2966-0-63765900-1314329103.jpg

That's cool.

Did you test just opening the <LabVIEW 2011 code in LabVIEW 2011 without compiling in LabVIEW 2011 first?

What was the result?

Cheers

-JG

Link to post

I did however realize that the red X on the property node vi was because I had made it a private function.

Cool, yep, its meant to do that.

I will try it without compiling, but will probably do it tonight.

Cool, I will try to fire up 2011 later on and check too.

Link to post

I've updated the library referred to by Mr Mike, it can be found here. When I use the palette included with the library, I get the red 'X' marks as shown in my previous post in this thread.

Link to post

I'd say no, I still see the red marks on my system with some of the menus from the library I posted. I can't say I understand why some have x marks and some don't. My Application palette does not have the glyphs, but the MessagePump one does. Both are in the same library, and the VIs have the same scope. There is no license associated with the library.

post-11742-0-58614400-1314623519.png

I will post this to the ni.com soon, just giving it a bit to see if it resolves over here first.

Link to post

Cool, yep, its meant to do that.

Cool, I will try to fire up 2011 later on and check too.

OK... so at the end of all this... is the behavior now what everyone would call "correct"?

If yes, does it match the documentation?

If no, what still needs tweaking?

Finally got around to checking it without recompile and it works as expected for me. Private function has an X and the public functions do not.

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By Zou
      I don't want to manually launch all installed LabVIEW versions one by one, and call this method.
      Is there a way to do this in one version to refresh palette for all installed versions?
       
    • By Steen Schmidt
      Hi.
      I have this 'Error & Warning' toolset with a functions and a controls palette:

      The controls palette contains only a single control, basically a subVI dropping its contents on the front panel when dragged there. That contents is two error clusters so I don't have to visit the control palette twice to get those (there are a small number of additional changes to these controls, mainly label and caption formatting to match GPower style). When dragged and dropped I have this on the FP:

      When dropping these it'd be nice if some additional stuff happened, like they automatically got wired to the correct connectors on the conpane (if they are available), maybe they placed themselves more conveniently than where you just happened to drop them etc. Now, I have been wrecking my brain about how to do make them do this. If I turn them into XControls it could probably be done, but I'd hate to turn something as fundamental as the error cluster into a proprietary XControl and litter those all over my (and other people's) VIs.
      I can't seem to get anywere with scripting on this one - the VI isn't being run when it spills its contents when dragged from the palette.
      Do you have any ideas, or is this too much work? I could maybe register some internal LV app event when the 'Error & Warning' toolset gets installed (it's a VIP), but that seems like a lot of work.
      Cheers,
      Steen
    • By David_L
      Hey all,
      As you may know in order to have a toolkit placed on the LabVIEW Tools Network it has to pass Compatible With LabVIEW certification. One of the requirements for the Compatible With LabVIEW program is that tools may not be located on the top palette, but should exist within one of the existing top-level categories such as Programming, Measurement I/O, Data Communication, etc.
      The reason behind this requirement is that the LabVIEW Palette can get quite bloated when you have many toolkits/modules installed. With just the full Developer Suite installed, there are over 20 top level palettes. Adding third party tools to this list will very easily bring the functions palette to grow off of the screen for a standard 1024x768 monitor. The secondary reason behind this is that this layout will help users find the functions more easy that will help them. For example if the user is looking for some data communication protocol, they are more likely to look in the "Data Communication" palette then in a sub-palette called "My Data Protocol" under a top level "DavidSoft Inc".
      I wanted to point this out so as you all start creating their toolkit for submission to Team LAVA or the LabVIEW Tools Network, you can take this into consideration ahead of time. However, with many things in our program, nothing is black and white. If there are special cases in which a toolkit especially should be on the top level, we will consider letting it go as such. One of these cases is OpenG. Since OpenG has a long-standing reputation and is known to be found on the Top level, it would be more hurtful than beneficial to require it moved to the Programming palette.
      If anyone has suggestions or ideas of other corner cases that would benefit from this top level location, or have comments or opinions for or against this policy, please feel free to bring them up here for debate/discussion.
      --David Out
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.