Jump to content

Christina Rogers

NI
  • Posts

    119
  • Joined

  • Last visited

  • Days Won

    13

Posts posted by Christina Rogers

  1. QUOTE(Jim Kring @ Sep 10 2007, 09:05 PM)

    I'm going out on a little limb here (by calling this a bug), but I can't see any good reason why the "Find Callers" dialog (right-click on ab LVClass and choose Find Callers) is not resizable.

    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.

  2. QUOTE(TiT @ Aug 9 2007, 02:50 PM)

    Who shall I direct the following request to ?

    I'd like to be allowed to bring my labview.INI file with me at the CLD.

    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

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

  4. I see a problem with that. After typedef edition, does the diagram constant keep its value (changing the displayed item string) or keep its displayed item string (changing the value)? There are circumstances where the former option is needed and others where it is the latter that is more appropriate.

    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.

  5. I fear for nasty bugs in existing projects when you change the behavior of a ring constant.

    Also execution speed could be inferior by adding extra features.

    The string info is not part of the data-type, please leave it like that. Please note that the combo box has a similar behavior.

    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.

  6. This is a good trick.

    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.

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

×
×
  • Create New...

Important Information

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