LabVIEW behaves strangely

[ggregson]

I am experiencing a problem in LabVIEW 2012 whereby some controls behave strangely. The graphview has lost its context menu even though it is enabled. Other controls are reporting a different labels than those assigned under properties. And I am unable to edit number controls. the code is a little large to post currently.

[GerdW]

Hi ggregson,

---

@ggregson wrote:

I am experiencing a problem in LabVIEW 2012 whereby some controls behave strangely.

…

the code is a little large to post currently.

---

Then you need to debug it on your own - what else do you expect for this amount of information?

(When the code is too large to attach it here in the forum, even after putting it in a ZIP file, then that file size might be a strong indication for the problems you are experiencing…)

[ggregson]

posted without the code first in case anyone had come across this problem before.

[wiebe@CARYA]

You're not giving us a lot to go on.

Did this suddenly occur?

Is this someone else's code?

---

@ggregson wrote:

 The graphview has lost its context menu even though it is enabled. 

---

Apart from being enabled, you can edit the run-time menus. (Advanced>Run-Time Shortcut Menu).

@ggregson wrote:

Other controls are reporting a different labels than those assigned under properties. 

---

Are their captions on (and the labels off)?

@ggregson wrote:

And I am unable to edit number controls.

---

This could be a lot of things.

Are they covered by something (a large decoration)?

Maybe they are grouped? (That will allow some editing)

Maybe the VI is in run mode (CTRL+m)?

Maybe the VI is locked?

[Bob_Schor]

So now you know that you need to supply a lot more information if you want more than a WAG (a colleague who worked for NASA once asked me if I knew the difference between a WAG and a ROM -- a Wild-Ass Guess and a Rough Order of Magnitude) from us.  I recommend a better description of the system on which you are developing (I'm guessing LabVIEW 2012 (32-bit) -- what OS, what major sub-systems, e.g. Real-Time, Vision, special DAQ), a compressed version of the entire Project (so we can really examine the code), and some hints of where we should look.

Bob Schor

[billko]

---

@Bob_Schor wrote:

So now you know that you need to supply a lot more information if you want more than a WAG (a colleague who worked for NASA once asked me if I knew the difference between a WAG and a ROM -- a Wild-Ass Guess and a Rough Order of Magnitude) from us.  I recommend a better description of the system on which you are developing (I'm guessing LabVIEW 2012 (32-bit) -- what OS, what major sub-systems, e.g. Real-Time, Vision, special DAQ), a compressed version of the entire Project (so we can really examine the code), and some hints of where we should look.

Bob Schor

---

Or what degree of education you would like in the guess.

[ggregson]

It  happened suddenly and no it is my code   i just didn't post as it is large and depends on hardware and i haven't had a chance to slim it down yet but I posted in case it was a known problem.

your first suggestion worked but i  wonder why the graphs suddenly lost their context menus.

the other suggestions were not applicable or didn't work..

[altenbach]

You might get corruption if the front panel or diagram is too large or shifted such that the coordinates of elements falls outside the valid I16 range. (details)

What is a "graphview"?

[wiebe@CARYA]

---

@ggregson wrote:

your first suggestion worked but i  wonder why the graphs suddenly lost their context menus.

---

Well, that shouldn't happen.

I'd revert from SCC to identify where it went wrong.

Something did cause this, and it seems to be some sort of corruption.

Did you do SCC merging? Usually VIs are treated as binary (and not merged), but IIRC this is based on heuristics so some VIs (with lots of text) might be merged anyway.

[ggregson]

 SCC merging? explain