Tab control problem !

[shpytza]

Hello there ! 🙂 I`m using labview 2011 , and I made a vi with loots of graphics , and I need them to be show in groups for each case that I studied . For that I used a Tab Control (indicator) , and after that I started to have problems . After each modification in the program ( delete a wire , move a object , rename a label , etc) the program freezes for 30 seconds . My question is : any other solution to group graphics so that I can show them for each case I studied ... I mean any other containers (or something like that) beside tab control , or is there a solution to the freeze problem because is starting to be really annoying , and takes me a lot of time to complete the program ! 

P.S.. Before I put the tab control (indicator) the LabView worked just fine 🙂 

[Ray.R]

That is interesting... 

I am working on a program that shares a similar issue of taking long to do a step such as create a new type def, modify an existing one or to save the VI's...  The program just happens to have a tab control.

I have no idea if this is related, but in my case, it is using LVOOP.

I hope you find a solution...  I get to drink too much tea as a result of waiting for the PC to catch up.

BTW, do you notice your CPU jumping to 100% while you have to wait?

[shpytza]

Yap my PC goes 100% 🙂 ...and still no solution ... (I think I will take the solution with tea just to calm my self down ) 

[Ray.R]

Does LabVIEW also switch to another window as described in this thread?

That's what often happens in my case.

[shpytza]

Yap, same thing ... It jumps of to the diagram block and back , or to the front panel and back 🙂 

[Darin.K]

I'd look into the picture ring and see if you can make that work.

[Ray.R]

I doubt that it is related to picture controls. Just saying that because I am not using that function.

Seems like a few people are reporting the same behavior in the other thread.

[Darin.K]

I am suggesting to use the picture ring instead of the wonky tab control.

It is actually pretty rare that I use a Tab control as Nature intended.  I either use just the tabs to control the content in a picture control, or I use the pages driven by a separate control or program logic.

Edit:  Third read, I see that graphics means controls.  I have only grinded the CPU with graphics, if controls cause this then I guess it could be subpanel time.  I would use the tabs to select which subVI is in the panel.

[oyester]

This is just a thought. I could be wrong.

Even though you are running different graphics on separate tabs, are you still computing the displays for all of the tabs. If so, you are using up CPU time for displays that the user isn't even looking at. If this is the case, you need to do something like wire the tab control to a case structure and just compute those things that are on the displayed tabl.

[shpytza]

I said,  before I used the tab control all the graphics where on the front panel ... And like I said the computer had no problems , and the program worked just fine 🙂  .... And from that I concluded it must be the Tab control