Jump to content

Christina Rogers

  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by Christina Rogers

  1. Do you happen to know off hand what other menu items it enables?


    To quote Greg McKaskle, "These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful. [...] If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LV left it. Don't ask tech support to fix it or complain that the LV attic has rusty nails and splinters." :-) But, if you really want to know, the token allows you to enable some features on subpanels that will most likely crash LabVIEW.


    Some of the decorations are now in the Silver Decorations palette in LabVIEW 2014. I wrote about them on my blog: http://blog.eyesonvis.com/?p=824


    The other way to get to the decorations is to copy them out of the parts of the Silver controls using the Control Editor.

  2. Would you mind going into detail a little about what is done for the improvement?  Mostly just curious and if your answer is "It's complicated" then that's fine with me.  


    We were just guessing at the Lava BBQ and we assumed that it was doing behind the scenes, what we were doing as work arounds.  Things like only updating cells you can see in the control, and only loading data for the cells you can see (so a table only has 10 rows show so it loads those 10 rows at a time with a fake scrollbar)


    Most of what I changed for listboxes in 2013 was related to calculating cell boundaries. From profiling the code, I discovered that a) when all rows were the same height, the algorithm for calculating a cell's bounds was slower than it needed to be and b) we were calculating cell bounds more often than we needed to. Since it's fairly common for all rows to be the same height, it was worth putting in an optimization for that case.

  3. The Tree Control is 10x faster!  :thumbup1:  :thumbup1:  :thumbup1:

    (At least, when I am setting cell colors on multiple rows while updates are deferred.)


    In my example, it was taking 4-5 seconds to do the update for a few 100 rows in LV2012.  In LV2013 it takes less than a second.

    This will be a big improvement for my GUIs.  So, thanks to the engineer(s) who worked on this!   :worshippy:


    I wonder if this is specific to the tree control or if other UI processing is also improved?


    You're welcome. :cool:


    (And sorry it took so long for us to find a way to address this).


    The changes that improved this performance were specific to the listbox, multicolumn listbox, table and tree controls. I don't expect that they will conflict with any "programming around the problem" tricks that you've used in the past.

    • Like 2
  4. There are no zero-pixel width splitters. (Sorry - I know they would be really useful).


    But Jack is correct that this should work without the top-level splitters.


    My recommendation is to avoid the VI property "Scale all objects on front panel as the window resizes." It almost never does what you want.


    Jack's example VIs work for me, but I'm guessing they are behaving differently for you because of this setting. I'm attaching a modified example that does not have that setting. Can you let me know if it works for you?


    Also, the "Scale Objects While Resizing" setting on the Pane (which Jack has set) is pretty important. It's not set on new VIs and it's in a really weird place (right-clicking on the scrollbar to get the shortcut menu with the Pane Sizing options).

    Container (1).vi

    Containee (1).vi

    • Like 1
  5. I gave away a couple advance copies of my graphic novel at the LAVA BBQ, and I'm pleased to share that the book is finally done and available for download or purchase!

    Anticipated FAQ:

    1. Who are you? I'm in LabVIEW R&D. I write the Eyes on VIs blog.
    2. What's a graphic novel? It's a story told in comic book format.
    3. Did you write it? Yes.
    4. Did you draw it? No. I illustrated it using 3D models rendered with a toon shader.
    5. What's it about? Here's the blurb: "500 years after the banishment of wizards, the kingdom of Valheigh faces the unthinkable: the rediscovery of wizardry and the return of the legendary evil known as the Jinn. A vengeful wizard unleashes the most horrific curse of Jinn legend such that Prince Rune must either kill the woman he loves or die at her hands."

    The PDF version is free and the printed book costs $25+shipping. I hope you'll check it out!


    • Like 1
  6. Or are you saying the current architecture of the LabVIEW source code won't lend itself to that without a major re-write?

    Unfortunately, that is what I'm saying. There is, as it turns out, a reason why we went without multi-select right-click menus for so long.

    it's kinda lame to just do the bare minimum and call it done.

    I agree it's less-than-optimal. I don't think of it as "done" but I can see your point that it might be hard to lobby for adding particular menu items. Is there anything that would make you more "delighted" without covering every available right-click menu option?

    Oh, BTW, I forgot to mention this earlier, but the multi-select right-click not working in the Control Editor (and thus also for LVClass private data) is a bug that has been reported and should be fixed in a future version.

  7. Unfortunately, the reason that this doesn't work the way you expect is that it was a lot more expensive to implement multi-select right-click menus than you would think.

    We don't have plans to put every right-click menu option into the multi-select menu framework, but if there are specific ones that you think have high value (e.g. common operations, operations not in Properties) then please let me know or propose it on Idea Exchange and I'll see what we can do.

  8. It's been a while since high school English, but with that corrective symbol, wouldn't the result be "Wierd" instead of "Wired", which I think is the intent?

    Here's an idea: could the switcheroo tool somehow be incorporated in the image for switching the letters around?

    ARGH! I blame lack of sleep from having a 5 month old baby. Yes, the squiggle is supposed to include the "R" with the "I."

    The switcheroo tool would be cooler. Maybe if we made the text vertical?

    I think she's making a reference to the "Keep Austin Weird" logo/saying that is part of the Austin, TX local culture.

    Yes! I actually toyed with the idea of a "Keep LabVIEW Weird" t-shirt for the R&D team, but never figured out what else I'd want on it.

    We could also use the "giant cow" that Stephen Mercer one day found staring at him while he was working on LVOOP VIs...;)post-5692-0-98415800-1305153282_thumb.jp

  9. The short answer is: "no, I think you're stuck with your workaround code."

    Longer answer: I found a CAR on this issue. It appears that the panel background images were never implemented to work with printing or the "Get Image" methods. There are some who argue that this is a reasonable behavior; after all, most web pages, when printed, will not print the background image by default. However, it seems to me that we should provide the option to print the background image. Unfortunately, adding such a printing option is not a trivial request, so I'm not optimistic about it being prioritized higher than other requests in the near future.

  10. Thanks, Michael. I verified my settings, verified that I was logged in, and everything works perfectly. *scratches my head* The only thing I can see that's different from when it didn't work yesterday is I'm on my home wireless instead of NI's. *shrug*

    It's a nice app, and it's sure to come in handy next week!

  • Create New...

Important Information

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