Difference between VI execution and executable.

[JTB]

I have a dynamic number of buttons within a cluster that I programmatically position on my front display based on the upper left position of the cluster.  When running in development mode, all is well and the cluster remains at that position after execution.  However, when the application is built, the buttons and the cluster get thrown to the left in a staggered fashion.  I've attached the zip file of the source.

[RavensFan]

Your zip file is missing some typedef's for the controls.

[JTB]

Just right click and disconnect from the typedef.  Both the cluster and the buttons.  It still fails in the same manner.  Thanks for looking into it.

[Matthew_Kelton]

If you did any error checking, you would see that at least one of the hidden properties you are using doesn't work in the executable.

[RavensFan]

---

@JTB wrote:

Just right click and disconnect from the typedef.  Both the cluster and the buttons.  It still fails in the same manner.  Thanks for looking into it.

---

Yeah.  I started to do that.  But there were a lot of them.  I got through them and then found there were dozens more hidden away that I couldn't get to in order to disconnect.

Sorry, but I can't help if you make it difficult or impossible to help.

[JTB]

Sorry, forgot about the typedefs for the buttons.  Here's the problem excluding all typedefs.  I also included a picture results of the VI running compared to the results of the .exe file running.

[Bob_Schor · Accepted solution]

I think the solution is very simple, and would have been more obvious except for the fact that you "hid" the offending code by using a Stacked Sequence (please, never use a Stacked Sequence).

In the "invisible" Case 0 and Case 2 of the Stacked Sequence, you write to the scripting Property AutoSize.  This property, in Execution Mode, is a Read-Only Property.  In general, any Property Node with the light-blue coloring that designates a Scripting Property, should (probably) not be in code that is intended for building as an Executable.

Bob Schor