Windows Front Panel Tearing

[mactierney]

Their is a major issue with my Labview VI's. I open the document and find that the scroll bars are missing even though there is content off of the panel. The front panel also 'tears' when I do a mouse scroll. I've gone through all the vi view options to make sure the scroll bars are visible and they should be. This problem has been posted in other posts too. I noticed that on all other threads TABS were used. Is this the cause of the issue.

See related posts:

http://forums.ni.com/ni/board/message?board.id=170&message.id=200310&requireLogin=False

http://forums.ni.com/ni/board/message?board.id=170&message.id=176426&query.id=43763#M176426

This is  a MAJOR glitch within labview. It happens for windows professional and vista. It has rendered most of our new code useless. We can't edit it with scrollbars and having one side of the front panel ghosting. The only workaround I know of is installing Labview 7.x and going through all the code to remove Lv8.0 code. I don't think that is a good path forward for NI as a solution. This bug should be considered a high priorty fix for NI. Our dept. is at a standstill with this problem and we're unlikely to relase our new code until this problem is fixed.

[mikeporter]

It seems the issue is related specifically to the tab control as shown in the example in the other thread. While opening that example does show the problem in V8.2.1. I have to this point been unsuccessful at building one that duplicates the issue. This sounds like a migration problem.

Sounds like to me all you have to do is recreate a couple top-level VIs that use the tabs and you're back on the air. While this might be a pain and should be not be necessary, I wouldn't call it something that is likely to bring an entire department to a "standstill".

By the way, I took the code that demonstrated the problem, copied everything from the block diagram and pasted it into a new VI - problem gone!

At worse, I would call this an "irritant".

Mike..

[mactierney]

Mike,

Thank you so much for your reply. I don’t think it’s a migration issue as we developed some of our top level VI’s exclusively in Labview 8.x and this problem only surfaced late in the development stages. We installed 8.2.1 this week and the problem is still there

Unfortunately it's more than a nuisance. This issue also exists in our executables so we cannot meet the deadline for our planned release. Some of our top level VI’s consists of a lot of code so copying and pasting to a new VI is actually not working. Yes, I’ve said it right, copying the block diagram to a new block diagram results in nothing appearing in the front panel, (except two funny looking boxes). I looked in the navigation window just in case I’m missing something, but it’s all gray. Double clicking on controls to find them on the front panel gives me nothing. And yes I waited a long time to make sure the paste went through.

Now, copying the front panel works if you don’t want any block diagram code. You basically get all your controls but no code.  So copying all our code to a new VI is a failure. We’re trying to consolidate some of our top levels into some subvi’s to see if we can still do this ‘copy/paste’ solution.

In the meantime though we’re stuck with the problem, especially as it exists in our executables so basically we can’t publish any of our VI’s until NI fixes this problem. This problem alone bumps it from a nuisance to a major issue.

I hope NI are working on this problem as hard as we're dealing with it. Thankfully they are aware of the problem from other posts.

Thanks again

John  

[Kalin_T]

Hi John,

I am really sorry your team is experiencing this problem. This was reported to R&D (# 3V5BLTOC) for further investigation.

Could you please attach a VI or a jpeg that demonstrates the issue? If you need more help please list your email so we can take this off line.

Best regards,

[mactierney]

Sarah, Ryan,

Thanks for your posts. They've been helpful and as Ryan mentioned some examples already exist (I posted them on this parallel thread:

http://forums.ni.com/ni/board/message?board.id=170&message.id=250861#M250861

Anyhow, we managed to fix the problem by using the Save as previous version' from 8.2 -> 8.0 -> 7.1. Had to install each version as you can only go back one version per install. Luckily had all the CD's handy. Of course we were using a lot of property nodes and functionality that didn't exist in 7.1 and came across quite a few 'insane objects' which we were able to flush out. Once we got a workable 7.1 version we opened it directly in 8.2, put all the lost code back in and presto, no screen splitting. In fact it's compiling quicker so I guess we'll have to leave it to the binary gods as to why this problem existed in the first place and what LV was doing in the background with handing this corruption.   

This, I believe, is a significant problem as you really can't tackle it via coding. It just sort of appears (having tabs may cause it?) And it's hard to reproduce, which hides any potential red flags.

Thanks again, and hopefully those of you who have this problem don't have too much "Reverse Engineering" to do to solve this problem

John