Jump to content


- - - - -

Suggestions for OpenG LVOOP Data Tools

closed review openg lvdata lvoop

45 replies to this topic

#41 Aristos Queue

    LV R&D: I write C++/# so you don't have to.

  • Premium Member
  • 2,324 posts
  • Location:Austin, TX
  • Version:LabVIEW 2011
  • Since:2000

Posted 07 February 2012 - 07:51 PM

*
POPULAR

Victory!

That output terminal will not be needed as of LV 2012. There was a (bug / unimplemented optimization -- depends upon your view) that made LV add a copy at certain upcast coercion dots. This compiler (fix / upgrade) will have performance benefits for a wide range of LVOOP applications. The change was implemented months ago, so this API doesn't get credit for finding the issue, but the compiler team verified your VIs do benefit from the change.

I would therefore recommend not putting it into the API as removing the terminal is a possible mutation issue, and not having the output terminal for a read-only operation is a much better API overall.

Edited by Aristos Queue, 07 February 2012 - 07:52 PM.


#42 drjdpowell

    Extremely Active

  • Premium Member
  • 305 posts
  • Location:Oxford, UK
  • Version:LabVIEW 2011
  • Since:1999

Posted 07 February 2012 - 07:58 PM

Oh good! Having to put those terminals in was annoying. I second the suggestion to go without the terminals. Though we might want a temporary note in the VI descriptions and/or on the block diagrams explaining this issue.

— James

#43 Aristos Queue

    LV R&D: I write C++/# so you don't have to.

  • Premium Member
  • 2,324 posts
  • Location:Austin, TX
  • Version:LabVIEW 2011
  • Since:2000

Posted 07 February 2012 - 08:00 PM

This same change will have effect of removing a copy on control refnums and .NET refnums also, although the effect will be much much smaller since the maximum amount of data copied in those cases is a single int32.

#44 neil

    Very Active

  • Members
  • PipPipPip
  • 209 posts
  • Location:Surrey, UK
  • Version:LabVIEW 2011
  • Since:2004

Posted 07 February 2012 - 11:24 PM

View Postjgcode, on 06 February 2012 - 11:44 AM, said:


It looks worse because of Icons and Text view - this is what it looks like as Icons only (in VIPM).

Attachment Palette VIPM.png

I would like to be able to change this is VIPM - if anyone else does too then check out and vote for David's cool idea (and my comment!) :) on the VIPM Idea Exchange.

I don't want to move stuff around too much due to palette inertia - but here is a second attempt for comment:

Attachment palette 2.png


possible thread derailment approaching!

While on the topic of OpenG pallettes, does anybody know an easy way to get rid of the "OpenG.." text at the bottom of all of my pallette icons? It never used to be like this...
My prefs are set to Category (standard) and all the other sub-pallettes do not have any text at the bottom. This started to happen a while (a year?) ago?

Note: this only seems to appy to the top level OpenG pallette menu, if I drill down deeper the text disappears

Attached thumbnail(s)

  • Attached Image: menus.png


#45 asbo

    The 500 club

  • V I Engineering, Inc.
  • 998 posts
  • Version:LabVIEW 2011
  • Since:2008

Posted 08 February 2012 - 01:19 AM

View Postneil, on 07 February 2012 - 11:24 PM, said:

While on the topic of OpenG pallettes, does anybody know an easy way to get rid of the "OpenG.." text at the bottom of all of my pallette icons? It never used to be like this...
My prefs are set to Category (standard) and all the other sub-pallettes do not have any text at the bottom. This started to happen a while (a year?) ago?

The most immediate downside I see to this is that if you use Quick Drop or the search functionality, you won't be able to see whether the VI in question is OpenG or not. Whether or not this is catastrophic is up for debate.

/derailment encouraging

#46 jgcode

    LabVIEW Renegade

  • Premium Member
  • 2,348 posts
  • Location:Australia
  • Version:LabVIEW 2009
  • Since:2005

Posted 29 February 2012 - 09:50 AM

Thanks everyone for their input - especially James for his donation of VIs.
This OpenG Review is now closed. Please start a new thread to discuss new changes to this VI. Please PM me if there are any issues with this thread.