Actor Framework Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Issues building executable

dsavir wrote:

This really should be better documented.

Is the 1634 error code not descriptive enough of the problem? I know it isn't something people want to wait until build time to discover, but I hoped that should have made it dead easy to diagnose once it occurred -- just check your error logs from your EXE.

Is there some better way to document this that you can suggest?

0 Kudos
Message 11 of 19
(1,710 Views)

AQ thanks for the information, I dont recall seeing an error 1634 when I attempted to run my application. At any rate, I went in and debugged the executable and after a little while I found the issue I was having.

Where would the error 1634 show up?

0 Kudos
Message 12 of 19
(1,710 Views)

AristosQueue wrote:

Is there some better way to document this that you can suggest?

How about adding a section to the "Read This First" page, where all guidelines/tips/potential problems are listed. It just needs to contain links to threads like this one.

Or a similar stick on this forum?

In any case, this current thread worries me more than anything else I've seen related to AF. If possible, I'd like to see some more on the recommended procedures (and potential pitfalls) for creating apps with AF and/or LVOOP.

Message 13 of 19
(1,710 Views)

Apologies for repeated posts; server acting up for me for the last while.

0 Kudos
Message 14 of 19
(1,710 Views)

DMurrayIRL wrote:

In any case, this current thread worries me more than anything else I've seen related to AF. If possible, I'd like to see some more on the recommended procedures (and potential pitfalls) for creating apps with AF and/or LVOOP.

There isn't really anything special about building EXEs out of AF or LVOOP. This one issue is a particular terminal on the Launch (Root|Nested) Actor.vi for opening the front panels. It only works in the development environment. We added it to facilitate debugging, but if you really want to open your panels at run time, you have to either set the panel to run when called or add an FP.Open call somewhere in your code -- like you do for any other VI. It is, honestly, the only issue that I know of. Everything else has been user errors (i.e. having dynamically loaded VIs that they forgot to add to their project, that sort of thing) -- nothing that is special about LVOOP or AF.

Message 15 of 19
(1,710 Views)

DMurrayIRL wrote:

How about adding a section to the "Read This First" page, where all guidelines/tips/potential problems are listed. It just needs to contain links to threads like this one. 

Done. Don't know if it will help, but done. 🙂

Message 16 of 19
(1,710 Views)

As I suspected, I made a "rookie" mistake 😃

Live and learn!

0 Kudos
Message 17 of 19
(1,710 Views)

In addition, I thought having this expained in the context/detailed help would be good. e.g. in launch root actor help on this input there should be in bold "In deployed applications set to False"

Thanks,

Danielle

"Wisdom comes from experience. Experience is often a result of lack of wisdom.”
― Terry Pratchett
0 Kudos
Message 18 of 19
(1,710 Views)

StevenHowell_XOM wrote:

I will just have to remember to not put a true constant on the launch root actor and make sure my actors that I want the front panels to appear, to change the settings in properties to do so.

I had same problem, thank you for posting this, I was wandering from last 8 hours.

-
Amit
CLAD
0 Kudos
Message 19 of 19
(1,710 Views)