Red X on Palette VI's

[klessm1]

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

[jgcode]

Yes, I have seen it before - you can read more about this issue here, here and here.

The CAR was #185059 and was fixed in LabVIEW 2011.

Cheers

-JG

[mje]

It was fixed? I still get them on several of my palettes.

[jgcode]

It was fixed? I still get them on several of my palettes.

Well that's what it says...

[mje]

/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:

[klessm1]

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.

[Aristos Queue]

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?

[jgcode]

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

[Mr Mike]

/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:

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.

[mje]

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.

[klessm1]

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).

[jgcode]

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).

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

[klessm1]

I did not try that yet.

I did however realize that the red X on the property node vi was because I had made it a private function. I will try it without compiling, but will probably do it tonight.

[jgcode]

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.

[mje]

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.

[Aristos Queue]

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?

[mje]

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.

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

[klessm1]

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.

[Mr Mike]

I can confirm the bad behavior mje's reporting. I didn't have all the icons that he has. I'll reopen CAR 185059.