LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

custom menu bar for windows 10

I think I've seen what you mean. At first, out of 20 runs, I got some residue of the old menu once. You see the items, but they are not functional. The new menu is functional.

 

It seems to happen more often after moving the window. Then I get about 50% result.

 

I doubt it's the timed loop. Why do you think so?

 

I did not see this happening at all after turning "Show front panel when loaded" off (in VI properties, Window appearance).

 

BTW. It's really annoying that the application removes itself from memory when you stop. Not sure how you can work like that. You should put the project in a project, and make a build specification. During development, don't close the front panel, and in an executable, do close the front panel. Even if you don't have the applicating builder, you should be using a project, and you should have a way to disable the FP close.

0 Kudos
Message 11 of 13
(616 Views)

the VI is a simplified version of the application.  It is part of a project and I built the source distribution from the project Build Specification.  I didn't send the project file.

I determined the issue was the timed loop by eliminating sections of code using Disable structures.  

The final application will be an executable that can be called from the Windows Desktop on other PCs.  The project file and associated files will remain on my development machine.

The solution seems to work for this simplified version.  I'll have to test it on the main application.

0 Kudos
Message 12 of 13
(597 Views)

I think it's just a weird timing problem in LabVIEW's internals. The timed loop is probably just something that is on the current critical path. The timed loop will have special threading features, so it could indeed be the cause.

 

Keep this in mind:

I did not see this happening at all after turning "Show front panel when loaded" off (in VI properties, Window appearance).

 

I think that might solve the actual internal problem, but if not using a timed loop works for you, I'm OK with that. I have never used a timed loop, except on cRIOs to synch with the scan engine.

0 Kudos
Message 13 of 13
(583 Views)