Blinking indicator different when compiled vs. development environment

[gmand]

Thank you! I suspected this, but wasn't aware that I can add my own entries to the .ini file of the executable. Here is the .ini file of the executable:

[FrontView]
server.app.propertiesEnabled=True
server.ole.enabled=True
server.tcp.paranoid=True
server.tcp.serviceName="My Computer/VI Server"
server.vi.callsEnabled=True
server.vi.propertiesEnabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
DebugServerEnabled=False
DebugServerWaitOnLaunch=False

So if I add the entries from my LabVIEW .ini file:

blinkFG=transparent
blinkBG=transparent

the executable should behave like the development environment? Is there way to add them during the bild?

[jcarmody]

This old post helped me when I wanted to add AllowMultipleInstances to my ini file.

[gmand]

Thank you, jcarmody! That worked.

Many thanks to everyone who replied! Let me summarize how I made this work:

In the VI's front panel, I set the indicator properties to Red when True, Transparent when False. In the block diagram, I set (via property nodes) the indicator to be blinking, and visible when True, and not visible when False.

Then hand-edited the application's .ini file to add these lines:

blinkFG=transparent
blinkBG=transparent
blinkSpeed=500

and now the application (when run from the .exe file) behaves as I wanted it to.

Following jcarmody's link to the old post, I was able to insert a custom .ini file during the build.