on button click stop on respect event in data diagram

[JÞB]

---

@crossrulz wrote:

---

@Bob_Schor wrote:

I agree with Jeff (I almost always agree with Jeff, except when I don't, and then I'm usually wrong ...).

---

Except for when Jeff is wrong...which does not usually happen since Jeff has a decent forums filter where he often does not open his mouth to remove all doubt that he is stupid.

Spoiler

"It is better to be silent and let people think you are stupid than to open your mouth and remove all doubt"

---

A lesson I learned the hard way.  Do not Drink N I !  

[altenbach]

---

kiwagh105@gmail.com wrote:

and my main question it if I click on button of front end (VI) how I can find the data diagram respecte to that button?

---

As a first step, you need to learn the basics of LabVIEW. It is useless to ask questions if you don't even know the terminology. There is no "data diagram", just a "block diagram". (The "data" is hidden inside wires, shift registers, front panel terrminals and such). There are no "forms", whatever that means (subVIs?). What odo you mean by "event" (thread subject)? A specific case of an event structure or something else?

You don't need to right-click and navigate a menu. All you need is double-click the control and you'll end up at the terminal. The right-click... find dialog is useful if you want to find associated property nodes and local variables but that usually starts on the diagram.

When you say "project", do you mean that in a generic sense or are you talking about a LabVIEW project (*.lvproj)?

What is your definition of  a "big project"? What is big about it? A few way oversized diagrams or many compact subVIs?

What does the program do? Does it interact with external hardware?

---

kiwagh105@gmail.com wrote:

yes I did this but terminals are isolated in digram not connected to any one and property node are connected to data other control but not understand how to stop there only after run

---

Where is "there"? You cannot stop after a run unless you mean something else with that term. You can configure the diagram to "retain wire values", meaning you can probe wires on the diagram even after the program has returned to edit mode and probe the lastet values. Make sure to turn that off later once you are done. Debugging subVIs might need even more skills, especially if they have debugging disabled or are reentrant, for example. do NOT modify system VIs, even temporarily (it is dangerous!).

If the terminals are isolated and values are written and read via local variables or value property nodes, it typically means that the code is poorly designed, most likely written by a text programmers with very litte LabVIEW knowledge. To avoide the race coditions associated with such a poor design, most likely there will be bandaid sequence striuctures everywhere to keep things corralled. 😉

The quality of the original code is a huge factor for determining how easy it will be to understand the code. Are there plenty of diagram comments? Is everything arranged in logical order or randomly scattered over a huge diagram covering many screens?

What are you supposed to do with this "project"? Just add a small feature? Fix a bug?  Rewrite from scratch? Take over development?

If you can, attach some code so we get a better picture of what you are dealing with..