02-20-2013 06:45 PM
So far I have been at a loss to narrow down this bug to a small example VI so here it is in general terms, in hope that somebody will have a solution to it.
I have an app with a large number of subVIs which I develop on a WinXP machine (LV 2012 latest patch). The main VI has a tab control with ten tabs in it (plus one hidden one). I have no trouble releasing it as a source distribution on a Win7 64 bit machine (running LV 2012 64 bits). Things work fine.
When I try to release it as a standalone app, the tab control disappears on the exact same machine where it works fine as a distributed source! Obviously it now installs as a 32 bits application, since I developed it on a WinXP machine...
If I release the same code on another WinXP machine (in fact a MBP laptop running WinXP from within Parallels Desktop), I have no trouble either...
Where did my tabs go on the Win7 machine?
I tried and checked whether a simple one-VI app with a tab on the FP would show the same problem, but that appears not to be the case... Nasty bug!
Solved! Go to Solution.
02-21-2013 03:11 AM
X,
do you use the same build script for the application on all machines?
What if you create a new build script on the Windows 7 64bit machine?
Norbert
02-21-2013 08:53 AM
I am using two different built scripts since the two outcomes are different, but the actual source files, etc are identical in both, so in this sense they are similar...
I haven't tried to create the executable on the target machine itself yet, but that won't in any case be exactly similar, since I have LV 64 bits installed on it.
02-21-2013 09:10 AM
I was interested in this because i thought it could be a corrupt setting in the build script itself.
The tab control is on the top-level VI or is it on some subVI maybe in a subpanel control?
Norbert
02-21-2013 11:16 AM
Top Level VI. The FP consists of a large Tab Control and in the built app, I can only see the content of one page. Obviously quite annoying 🙂
02-21-2013 12:00 PM
Does changing the style of the tab help or not?
02-21-2013 12:51 PM
What do you suggest? I use the Modern style Tab (wished there was a Silver one!) and paint it with "System Color". Do you mean using a "System"or "Classic" Tab instead? I can try that, but only if you justify it with some insider info...
02-22-2013 04:06 PM
Changing tab style has no effect (fails just as bad in a standalone app).
Morevoer, I have been able to verify that the tab also disappear on a Windows 7 32 bits system. In summary:
Standalone Windows XP (32 bits): tab OK
Standalone Windows 7 32 bits: tabs disappear
Standalone Windows 7 64 bits: tabs disappear
02-23-2013 01:30 PM
@Norbert_B wrote:
X,
do you use the same build script for the application on all machines?
What if you create a new build script on the Windows 7 64bit machine?
Norbert
I finally got around to create a build script on the target 64 bit machine.
The released application DOESN'T SHOW the tab either!
It looks like my tab doesn't want to show on ANY Windows 7-released app, but shows up fine as a VI run from within LabVIEW...
02-23-2013 02:54 PM
I am attaching a stripped down version of my app.
The archive contains:
- a folder within which you'll find the project containing the top VI and the build script I am using
- a folder containing the necessary VIs/ctl (mostly the latter as I removed most of the innards)
- the application folder with the executable
If you run the VI from within the project, it shows a FP consisting of a Tab with multiple pages. You can browse the pages if you wish. Nothing is functional, so that's basically just a template.
If you now quit LV and run the app itself, you'll see a FP devoid of any page beside the first one. Where did the other pages go?
I tested this on my Win7 64 bit machine.