LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 8 bug?: reusing custom controls with imported graphics



@jpeters wrote:

I have a pretty good idea of what is going on, but I still cannot reproduce the corruption so I still can not really understand the cause of this.  You get the "d" image because the VI is saved (somehow) referencing that image -- that image is one of LV's built in images, the decimal radix image.

I tried your new steps and looked at your application.  I still cannot reproduce the corruption.

Jeff P




Now that you mention it, that is another thing that is wrong with my LV8 build.  Attached are two screenshots of my application, one built with LV711 before I installed LV8, and one built with LV8.  Not only are the imported pictures missing, but the radixes are missing too.  By default, the dec radix should have been visible.
 
What you are seeing is a tab control with three pages, each page has what you see in the snapshot.  That is a cluster of 16 clusters, the bottom 8 set to disabled = 2 programatically.  Each of the 16 clusters has 2 custom buttons each with a different imported picture plus a numeric.  The text that you see in the 16 clusters is a caption that belongs to the numeric and it is also set programatically.
 
[Editted because I quoted the wrong post.]

Message Edited by mochalatte on 02-09-2006 03:57 PM

Download All
0 Kudos
Message 21 of 39
(1,627 Views)


@jpeters wrote:

Just to be clear:  if you unzip the application attached -- you see the problem?  Because I don't.  

Jeff P




Yes, I verified it by clicking the test5.zip I uploaded to the message board and ran it from the open zip.
0 Kudos
Message 22 of 39
(1,617 Views)


@mochalatte wrote:

 clusters, the bottom 8 set...


Er, should have said 12
0 Kudos
Message 23 of 39
(1,603 Views)

Ok so I now see the problem in the application...  If I cannot reproduce the point of corruption though I don't think I can provide a fix.  Can you attach your .ini file -- perhaps there is something in there that is causing it.  I know that you have reproduced this on a couple of machines, so I doubt it, but it is worth a shot.

 

Jeff P

0 Kudos
Message 24 of 39
(1,604 Views)
Here it is.
0 Kudos
Message 25 of 39
(1,597 Views)
I've uninstalled everything NI, cleaned the registry, and now I'm reinstalling LV8.  I would like to take any interesting "snapshots" I can of the installation as I take steps towards repeating the corruption event.  Is there anything in particular that I should be looking at?
0 Kudos
Message 26 of 39
(1,575 Views)
I uninstalled LabVIEW711 and 8 and all other NI stuff, cleaned up the registry, and started reinstalling things and eventually reproduced the problem.  I did so without ever opening or running any of my old VIs.  Specifically, everything I opened or built in LabVIEW I created from scratch today.  Here's a detailed blow-by-blow:
 
1. Uninstalled everything NI and IVI, rebootted, manually removed most of the stuff in c:\program files\national instruments, cleaned the registry with TweakNow, rebooted, and installed LabVIEW 8 with the run-time engine.  Didn't install anything from the driver disks yet.  Rebooted.
 
2.  I tried building a simple vi with a custom control with imported graphics.  I created a new project and built an exe--it worked fine.  I created an installer and installed it--the result in c:\program files worked fine.
 
3. I created a more complicated vi with nested clusters and a button with imported graphics and a numeric with its radix shown.  (See the attachment "the vi before building.png")--still no problems with a build.
 
4. I added a tab control and put three copies of the cluster in its pages--still no problem.
 
5.  Next I installed the NI drivers from the 2 disks, installing everything selected by default plus NI serial & IVI compliance.
 
6.  I copied the last VI and its controls into a new folder, created a new project file for it, and built it.  When I ran it, I first saw the problem again.  (See the attachment "it happened again.png")
 
7.  For consistancy, I created a fresh VI and project and built it, and yes, it seems to be a permanent change to my LabVIEW development environment.  It seems that I am again in a state where I cannot successfully build a project containing more than one copy of a custom control with an imported picture.
 
8.  I uninstalled everything Nat Inst and everything IVI, but this time I didn't manually delete files nor did I clean the registry.  I reinstalled LabVIEW8, again NOT installing the driver disks.
 
9.  I again copied the VIs from #4 & #6 above into a new folder, created a new project, built and ran and did NOT see the problem.
 
Just to be clear, I never did install any toolkits today.  It seems that the problem started after I installed drivers and tried to build a VI involving nested clusters, a custom button with imported graphics, and a numeric with its radix turned on.
 
I've attached the VI and project where I saw the stretched-d graphic today.
Download All
0 Kudos
Message 27 of 39
(1,560 Views)

This is a great help.. I really appreciate you patience in this matter.  I will try the steps that you have given and see if I can (finally) reproduce it.

 

Thanks a bundle.

 

Jeff P

0 Kudos
Message 28 of 39
(1,554 Views)
Picking up from where I left off above,
 
10.  I installed only some of the drivers on the 2 disk set:  mainly GPIB & Visa stuff that I need for my application.
 
11.  Tried rebuilding my test project--had no problem.
 
12.  I added some more drivers, including IVI compliance pkg 2.3 (just LV8 support)
 
13.  Tried rebuilding my test project--DID have the problem.
 
14.  Uninstalled IVI compliance pkg only.  It didn't even ask for a reboot at the end and I didn't reboot.
 
15.  Tried rebuilding my test project--did NOT have the problem.
 
It seems like I'm pinning at least some of the blame on the IVI compliance package 2.3, which is a shame because I think I need it.  I've used both the generic IVI DMM and IVI PS in my application.  Is there something other than the IVI compliance package 2.3 that I can install to be able to get up and going again?
0 Kudos
Message 29 of 39
(1,547 Views)
Just to keep things confusing...
 
16. Install the toolkits that I want:
 
Advanced Signal Processing
Database Connectivity
Internet
SPC
PID Control
Report Generation
State Diagram
VI Analyzer
 
Rebootted.
 
17.  Try another test build and the daggum build problem has returned even though I didn't reinstall IVI compliance pkg.
 
18.  I uninstalled all of the toolkits with uninstallers (all of the above except "State Diagram").  Rebootted.
 
19.  Try another test build, and the problem has gone away again.
0 Kudos
Message 30 of 39
(1,537 Views)