From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"Start Asynchronous Call" as it should be

Neat.  Yeah I've abandoned all LLBs for a while now.  Everyone I find in my development I usually flatten into a folder.  As for why the VIPM won't build I couldn't figure it out.  I posted on the JKI forums asking for help and attached the build spec there.

0 Kudos
Message 41 of 52
(1,214 Views)

@Hooovahh wrote:
...

The only one I'm having problems with at the moment is the Compare to Constant.  If I try to build with it in the package it errors out saying it can't find files that are definitely there.  I'll keep messing with it to see if I can get it working.


Look in the ability SelectMenu5.vi.  Try changing that malleable vi to Coerce To Type.  See if that helps.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 42 of 52
(1,177 Views)

@paul_cardinale wrote:


Look in the ability SelectMenu5.vi.  Try changing that malleable vi to Coerce To Type.  See if that helps.


Nope but thanks for the suggestion.

0 Kudos
Message 43 of 52
(1,156 Views)

Oh boy thanks Paul for the suggestion, it now builds and here is an updated package which is the same as the last, but it now includes the Compare to Constant XNode.  You might want to consider posting these over the Code Repository on LAVA.  I don't mind providing the VIPM config I've been using so you can maintain it.

Message 44 of 52
(1,128 Views)

Beautiful! Wish I could kudo more than once!

0 Kudos
Message 45 of 52
(1,037 Views)

@ConnerP wrote:

Beautiful! Wish I could kudo more than once!


I'll do it for you!

0 Kudos
Message 46 of 52
(1,026 Views)

GAAA!!  Bugs!

I found and fixed the following bugs:

  1. In "LVObject MethodSelector.xnode"
    1. It wasn't seeing methods that were in virtual folders, only those at the root of the class library.
    2. It was showing methods without regard to access scope.  Not it only shows methods that are allowed in the scope of your BD.
  2. In "Index and Unbundle.xnode", this nasty one:

ibb.png

The complete updated set is attached.

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 47 of 52
(953 Views)

Well that was bad.  I introduced a new bug that ruined it.

Here's the fixed up version.

"If you weren't supposed to push it, it wouldn't be a button."
Message 48 of 52
(919 Views)

Upgrade for "LVObject MethodSelector.xnode"

The previous version would only show methods of the wired class,

This version shows the methods of the ancestors as well.

"If you weren't supposed to push it, it wouldn't be a button."
Message 49 of 52
(817 Views)

Here's an upgrade for "Asynchronous Call.xnode":

  • Bug fix pertaining to preserving state info when updating from an earlier version

  • Much better help (now includes the name, location,  and description of referenced VI).

  • Icon now indicates if the referenced VI is broken.

  • Reloads the referenced VI less often

  • Much less finicky when the referenced VI is broken (for instance it wouldn't show the terminals if the VI was broken)

I've also included a new one: "Call By Ref in Other Context.xnode".

 

Now, can anybody figure out how you can make it so you can step into these?

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 50 of 52
(679 Views)