Another LabVIEW bug? Event Structure Pull-down List does not show up...

[X.]

Pretty sure.

Moreover, as I said, the glitch came and went on the other machine on which I have updated everything there had to.

Most annoying but it might well be a video driver bug.

Not sure why it does that with my Event Structure but not the corresponding Customer While Loop which has exactly if not more cases and therefore a longer pull-down list of cases...

Keep in mind though, that I am using a 2048x1152 display (including on this new machine).

[NetoNI]

Hello,

Can you tell me which LabVIEW version are you using? Also could you upload your more recent code here to see if I can reproduce the error.

Thanks.

Ernesto

[X.]

LV 2013 SP1 (both 32 and 64 bit on both XP and 7).

My code is way to large to be uploaded. But I don't think it is a matter of code, rather of having a largelist of events (93 and counting in my case) and a large screen (mine is 2048x1152 and I am using a VGA connection to it for quirky reasons).

As I said, but since it is very irreproducible I would not make a strong point of it, it seems to happen only with the Event Structure. The corresponding Case Structure in a different loop, which has more cases, never exhibited this problem.

[NetoNI]

Hello, 

Could you copy that specific event structure in a new .vi and see if the issue keeps happening? If  the issue is still there could you send me that .vi please?

Regards

Ernesto

[X.]

I certainly appreciate the intention of the request, but simply copying and pasting the Event Structure is not going to cut it as most event cases get emptied in the process and the whole code gets broken.

I am not 100% sure this is a LabVIEW bug, and it is very unpredictable (therefore me confirming that the dumbed-down VI does show the problem may take weeks).

It might not be worth investing much time investigating, especially if I am the only one to cope with it.

My only intent was that a developer very familiar with the graphics rendering innards of LabVIEW be aware of this report, just in case that code might have some well-known boundary condition issues (or memory leak or what not), or not so well-known ones...

With 4K displays around the corner, this might be become more prevalent...or again, not.

Let's call it quit until I find some way for you guys to reproduce it, if ever.

[NetoNI]

Hello, 

Ok. Thank you for the information. Good luck with your project.

Regards

Ernesto.