Christina Rogers

[Posted on behalf of Aristos Queue because he can't reply to his own post without the messages joining together] Answer to Q1: Yes. The "Not A Number/Path/Refnum" function not only tests if the refnum value is equal to zero, it also checks to make sure the refnum is a valid refnum. Thus if you have a non-zero refnum but the refnum has been closed/released then the "Not A Number/Path/Refnum" function will return true but the "Equals" function will return false. Answer to Q2: No. A block diagram constant of a refnum type always has the value "Not A Refnum," unless you count the special case of the "Static VI Reference" which is not really a constant.

QUOTE (crelf @ Jul 29 2008, 01:26 PM) Actually, they screwed up thrice which is why I gave up on them being able to handle this order correctly.QUOTE (crelf @ Jul 29 2008, 01:26 PM) We used to use CafePress, but they limit each item type [...] unless we open a store and pay them a whole lot of money ). CafePress stores are free now, but if everyone else is happy with zazzle, then stick with what works. QUOTE (crelf @ Jul 29 2008, 01:26 PM) Christina: don't give up! I suggest you give zazzle a call, explain the situation, and they might be able to get you a new shirt before NI-Week. Given the flimsy, under-sized ladies shirt that they sent me, I have no reason to believe they can make one of reasonable quality, especially with the remaining time. I might call them to ask for a refund. Just don't give me any crap for not having a shirt at the BBQ! I tried. Ever since I saw this blog post about how tech shirts are all-too-often female-unfriendly, I decided I want women's shirts whenever I have a choice (although for me it's not a size issue as much as a fit issue). QUOTE (crelf @ Jul 30 2008, 09:01 AM) I'd be too frightened that Christina would slap me at the BBQ... You all are lucky I save my fiery wrath for coworkers who break user interface design rules. addendum: Zazzle sent me an e-mail offering to print a shirt without waiting for the return, but they're all out of Ladies XXL shirts, so I'm going to pass.

QUOTE (jgcode @ Jul 28 2008, 01:16 AM) Try the example instead: C:\Program Files\National Instruments\LabVIEW 8.5\examples\lvoop\Navigation\Navigation.lvproj main.vi has the same look as the GSW.

OK, so first Zazzle forgets to ship my Ladies shirt with our group shipment and Stephen has to contact them to get them to send it. Then it arrives and, as Stephen says, the thing is the smallest XL I have ever seen. I seriously think it might have been a child's shirt. So I exchange it for a 2X, hoping for the best, and they send me a 2X men's shirt! It looks like I'm wearing a tent. There isn't enough time to exchange it again before next Tuesday, so I give up. I am never buying anything from Zazzle again, so please consider a CafePress alternative if you do t-shirts again next year.

QUOTE (Justin Goeres @ May 21 2008, 04:36 PM) I just picked up my NIWeek badge and the image is 1.4 cm high and slightly more than 1.6 cm across.

QUOTE (crelf @ Jun 15 2008, 09:23 AM) I'm planning to order the Ladies Basic T-Shirt in Black. I hope that's an acceptable customization.

You might look at <LabVIEW>\project\procmphier.llb\CMP Compare two VIs.vi Standard disclaimers apply, e.g. about how NI can change VIs in the project folder without warning, yada yada yada.

Currently, you can't add items to the GSW. You can only replace them. That's because I haven't written anything to make the background dynamic. So you're going to have to remove one of the existing items in whatever section you want your new link to appear. The multiple backgrounds Aristos mentions won't help here. There are three (Windows w/o Target modules, Windows w/ Target modules, and Mac/Linux) backgrounds because the Targets ring and the Search bar are only shown with Target modules and Mac/Linux, respectively.

Duplicating my response to Jim's comment on my blog directing me to this thread: PS CAR# 96951 was marked as a duplicate of CAR# 49855.

Hi Justin, I'm sorry to say, you can't remove a password-protected VI from a library without providing its password (and the library's password, if it's also password-protected). LabVIEW shouldn't have let you add the VI to a library without providing a password. That was a bug. Do you have a backup of the VI? - Christina

Both of those features are in LabVIEW 8.5.

Jim, Do you think that removing the file extensions would get confusing to some folks? I am concerned that the icons in the project aren't distinct enough. - Christina

In LabVIEW 8.5, you can use Save As to move a project file. If the option is disabled, it may be because you have unresolved conflicts in your project.

Here's the KnowledgeBase article. It seems to be missing the keyword "typedef." I'll see if I can get that fixed.

QUOTE(Jim Kring @ Sep 10 2007, 09:05 PM) I won't split hairs on what we call bugs, but I agree that the dialog should be resizeable, and I wouldn't be surprised if it became that way in some future version.

QUOTE(Jim Kring @ Sep 10 2007, 09:48 PM) I created a simple test project and "Save All (this Class)" on the parent class did not save VIs in the child class unless those VIs were referenced by VIs in the parent class. I think AQ's description of the functionality is correct.

QUOTE(TiT @ Aug 9 2007, 02:50 PM) Sounds like a reasonable request. I'll forward this thread to the folks in our customer education department. You might also talk to your sales representative. As you probably know, customer success is very important to NI (have you seen Dr. T's triangles?) and we're happy to hear suggestions of what we can do to help you. - Christina

LabVIEW 8.5 didn't actually change the palette layout. (Well, we added some things, but the main layout didn't change). The thing that changed was that LabVIEW 8.0 and 8.2 tried to see if you had an older LabVIEW installed on the machine and changed the visible palette categories. For a variety of reasons, this didn't work so well. You can copy the INI file from your previous 8.x version of LabVIEW and you should, for the most part, feel right at home in 8.5. I agree this should be easier, and I've talked to a few people at NIWeek about how we could improve the upgrade experience to preserve the user preferences. The top-most visible category is the one that is automatically expanded when you right-click and get a temporary palette. But you have to pin a palette to change the visible categories (as I said on my blog and as was pointed out in this thread). - Christina

The Express palettes are the default in LabVIEW 8.5. That's what you'll get with a fresh install (or if you delete your INI file). Now you all know why I posted a blog entry about how to customize the visible categories in the palettes. (Sorry the videos on my blog are currently unavailable. I'm working on getting a new home for them). - Christina

That's actually a separate problem. Currently (and I'm not planning to change this), a ring constant will preserve its numeric value and an enum will preserve its name.

Just to clarify, I'm not suggesting we would change rings in any way. The only change would be constants that are linked to strict typedefs updating at the same time that front panel instances update. That means when their time stamp is out-of-date instead of when their type is different. So this would only affect load time, and have no effect on execution speed at all.

Keep in mind that you must have all your typedef instances in memory for this technique to work. The short answer to why this is not a bug is: Typedefs only update on type changes. Strict typedefs update on all changes (including cosmetic modifications) Ring text is not part of the data type. Enum text is. There no such thing a strict typedef on the diagram.* Now, being a usability advocate, I'm going to argue that "working as designed" doesn't mean it's right. The LabVIEW team has been struggling with how to fix this problem. Would anyone be opposed if we changed it so that constants that are linked to strict typedefs update on all changes, the way front panel instances do? The downside is that you have no control over what a constant from a typedef looks like. So, for example, if you create a constant from a strict typedef cluster and then resize the constant, whenever the constant updates you lose your resizing. - Christina, LabVIEW R&D * - The reason constants of strict typedefs are demoted to non-strict typedefs is because "strictness" generally applies only to cosmetic attributes which are meaningless on the diagram. I think the use case for rings was not fully considered, and that's part of why we're considering changing it.

transparentBDFreeLabels=True I can't remember if this is in 8.0, but I know it's in 8.20. (In case you're curious, Jeff Kodosky himself requested it, which does help override objections). It will probably make its way back to Tools>>Options in a future release. Christina Rogers LabVIEW R&D http://eyesonvis.blogspot.com/

I mentioned "bird's eye" so people would know what I was talking about (and not confuse it with the old Navigation dialog). Yes, I know there's a neat-o OpenG bird's eye, too. I remember when it came out (just before mine went Beta) and I checked it out and found in its subVIs that we had shared the same inspiration: the scaled panels and diagrams that went into the New file dialog in LabVIEW 7.0.