VI distribution without using AB

[doobs]

I've just now gotten off the phone with the bad news. The enable/disable
functions of the tabs in a tab control are broken when a vi is created into an
executable with the application builder.

As I have just finished building a large scale app around a tabbed interface
and really don't wish to we-write the thing, I was wondering what my options
might be.

Aha I thought, I'll use the LabVIEW player to play the vi. Unfortunately,
although the player is available, the tools to apply a digital signature to a
vi are not anticipated to be ready until next month.

As I see them, my options at this point are;

1) Rewrite the app around the tab example given for ver 5.0.
2) Buy a copy of the base LabView and give it to my cu
stomer

Does anyone else have any brilliant ideas on how to get a working app to a
customer with as little effort (and expense) as possible?


===========================================================================
SolidWorks Research Partner National Instruments Alliance Member

Christopher Dubea Phone: (504) 847-2280
Vice President of Engineering Fax: (504) 847-2282
Moving Parts L.L.C. email: cdubea@movingpart.com
P. O. Box 6117 URL: http://www.movingpart.com
Slidell, LA 70469-6117

[CraigGraham]

Chris Dubea wrote in message
news:h8ql1t4k9206vpjlu65q0stisn9rbjnprk@4ax.com...
> I've just now gotten off the phone with the bad news. The enable/disable
> functions of the tabs in a tab control are broken when a vi is created
into an
> executable with the application builder.
>
> As I have just finished building a large scale app around a tabbed
interface
> and really don't wish to we-write the thing, I was wondering what my
options
> might be.

Perhaps I'm being idealistic, but have you tried coming to an arrangement
with NI whereby you can give the required components to the customer without
having to pay the full whack? Afterall;

1) The customer I assume is hardly likely to use Labview as a programming
language, and I assume in any cas
e the wiring diagrams, along with all
unnecessary components like Labview documentation, examples and
unnecessaries from vi.lib will be removed, making it extremely difficult to
start playing with it.

2) This problem has arisen as a result of a cockup by NI, and the
responsibility lies more with NI than with you. Certainly there's nothing
legal you can do about it, but NI appear to be quite reasonable. In
addition, unlike for example Microsoft, they do not hold a monopoly
position, there are alternative programming environments to Labview, and
NI's user support is a factor in deciding which approach a company should
take for a project.

I, and probably others, will be interested to hear how this pans out.

[Andrew Johnson]

Chris Dubea wrote:

> As I see them, my options at this point are;
>
> 1) Rewrite the app around the tab example given for ver 5.0.
> 2) Buy a copy of the base LabView and give it to my customer
>
> Does anyone else have any brilliant ideas on how to get a working app to
> a customer with as little effort (and expense) as possible?

I would vote for re-writing the tabbed interface in the "old" manner. I
do this with hidden booleans covering architectural booleans that dip or
rise depending on their state, and wire the invisible booleans to a
radio control subVI.

It shouldn't take too long to rework things this way.

Unless the customer has an interest in learning labview, but then they
get to see your source code, unless you hid
e each subVI's diagram in
some manner.

- andrew johnson
- Wireworks West
- Berkeley CA US

[Kyle_Gupton]

Hold on! This bug is fixed in the upcoming LabVIEW 6.0.1 patch that will
be available *very* shortly. I just verified it myself.

Kyle Gupton
National Instruments