Jump to content


Photo
- - - - -

Conflict resolution


  • Please log in to reply
10 replies to this topic

#1 jzoller

jzoller

    Very Active

  • Premium Member
  • 263 posts
  • Location:Colorado, US
  • Version:LabVIEW 2011
  • Since:1998

Posted 21 January 2011 - 04:12 PM

:frusty: Resolve_Please.png

<sigh>... I wonder which path to choose?

Edited by jzoller, 21 January 2011 - 04:13 PM.


#2 crossrulz

crossrulz

    Extremely Active

  • Members
  • PipPipPipPip
  • 254 posts
  • Location:Cincinnati, OH
  • Version:LabVIEW 2011
  • Since:2004

Posted 21 January 2011 - 05:01 PM

decisions decisions...

I bet you can't select to use either one (I noticed the "Use Selected Item" button was greyed out).

#3 george seifert

george seifert

    Extremely Active

  • Members
  • PipPipPipPip
  • 399 posts

Posted 21 January 2011 - 05:05 PM

:frusty: Resolve_Please.png

<sigh>... I wonder which path to choose?


Let the force guide you my son.

#4 Val Brown

Val Brown

    The 500 club

  • Members
  • PipPipPipPipPip
  • 702 posts

Posted 21 January 2011 - 05:53 PM

Well you are waiting...on an error...hmmm how Common is that????
All of my objects are byval

#5 jzoller

jzoller

    Very Active

  • Premium Member
  • 263 posts
  • Location:Colorado, US
  • Version:LabVIEW 2011
  • Since:1998

Posted 21 January 2011 - 07:08 PM

decisions decisions...

I bet you can't select to use either one (I noticed the "Use Selected Item" button was greyed out).

Yep, the problem went away when I quit LV...

Let the force guide you my son.

If I get lightning, I'm going dark side. Sorry.

Well you are waiting...on an error...hmmm how Common is that????

Someday, Wait (ms) may have error terminals. :beer_mug:

#6 crossrulz

crossrulz

    Extremely Active

  • Members
  • PipPipPipPip
  • 254 posts
  • Location:Cincinnati, OH
  • Version:LabVIEW 2011
  • Since:2004

Posted 21 January 2011 - 07:20 PM

Someday, Wait (ms) may have error terminals. :beer_mug:


The idea has enough Kudos. But still wait for the "In Development" status to come up.

#7 ShaunR

ShaunR

    LabVIEW Archetype

  • Members
  • PipPipPipPipPipPip
  • 2,224 posts
  • Version:LabVIEW 2009
  • Since:1994

Posted 21 January 2011 - 07:40 PM

The idea has enough Kudos. But still wait for the "In Development" status to come up.

+ 1 kudos. And while they're at it they can do the same with tick count, and wait next ms tick.
A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort. (Herm Albright 1876-1944).

Founder and general mischief maker on www.labview-tools.com.
SQlite aficionado and websocket zealot.
If it 'aint in LabVIEW, then you 'aint got a clue!

#8 Darren

Darren

    Extremely Active

  • NI
  • 398 posts
  • Location:Austin, TX
  • Version:LabVIEW 2012
  • Since:1999

Posted 21 January 2011 - 08:14 PM

*
POPULAR

+ 1 kudos. And while they're at it they can do the same with tick count, and wait next ms tick.


I added VI wrappers with error terminals for Wait (ms), Wait Until Next ms Multiple, and Tick Count in LV 2011. Look for them in vi.lib\Utility\timing. They're not the ideal solution, but until we get error terminals on the primitives, at least we can stop having to worry about maintaining our own copies.

-D

#9 ShaunR

ShaunR

    LabVIEW Archetype

  • Members
  • PipPipPipPipPipPip
  • 2,224 posts
  • Version:LabVIEW 2009
  • Since:1994

Posted 21 January 2011 - 09:07 PM

I added VI wrappers with error terminals for Wait (ms), Wait Until Next ms Multiple, and Tick Count in LV 2011. Look for them in vi.lib\Utility\timing. They're not the ideal solution, but until we get error terminals on the primitives, at least we can stop having to worry about maintaining our own copies.

-D

I would suggest replacing them in the palette (like the space constant ;) '). I've been using my ones for over 10 years so it's not really a maintenance issue, I appreciate the thought, but really the primitives need to be changed.

Edited by ShaunR, 21 January 2011 - 09:07 PM.

A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort. (Herm Albright 1876-1944).

Founder and general mischief maker on www.labview-tools.com.
SQlite aficionado and websocket zealot.
If it 'aint in LabVIEW, then you 'aint got a clue!

#10 Darren

Darren

    Extremely Active

  • NI
  • 398 posts
  • Location:Austin, TX
  • Version:LabVIEW 2012
  • Since:1999

Posted 06 April 2011 - 11:21 PM

Looks like I spoke too soon. Based on some beta feedback, and after discussing the issue further in-house, I will not be including these VIs in 2011. Hopefully, we'll see native support for the error terminals on the primitives themselves in a future LabVIEW version (go vote for this idea if you haven't already). For posterity, here are the VIs I *almost* shipped in 2011, zipped up and saved in LV 2010. :) And of course, there's also the option of using the OpenG Time Tools VIs.


-D


Attached Files



#11 jgcode

jgcode

    LabVIEW Renegade

  • OpenG
  • PipPipPipPipPipPip
  • 2,397 posts
  • Location:Australia
  • Version:LabVIEW 2009
  • Since:2005

Posted 07 April 2011 - 01:03 AM

Looks like I spoke too soon. Based on some beta feedback, and after discussing the issue further in-house, I will not be including these VIs in 2011. Hopefully, we'll see native support for the error terminals on the primitives themselves in a future LabVIEW version.


Time for another campaign? :)