10-15-2022 11:04 AM
This thread is still going, after two weeks, with a lot of words but very little (meaningful) communication. @3d0g has a code problem that seems to involve Graphs, Tab Controls, more-than-one Event Loop, and very little "give" on the part of the Original Poster (or OP) -- in particular, despite numerous requests that the OP help us to understand the problem by posting code, the OP responds with another long missive about LabVIEW and "how it should be organized", apparently ignoring the offer for help.
There are many things about the OP's code that are hard to discern. Is it organized in a LabVIEW Project? Are the VIs and other LabVIEW structures (such as TypeDefs) in the Project also organized in a similar fashion on disk? [This means that if your Project, when opened, shows Folders and items in Folders, is there a comparable structure of Folders/files on disk? If so, that makes the "Bundle the Project" step simpler].
Here's what you should do, to get you a definitive "better code" (which you can then ask, "Why did you do Such and Such?", and thereby learn the thinking behind LabVIEW). Note that this assumes that you have a Folder called "My Project" on disk, inside of which is "My Project.lvproj" and all of the LabVIEW code that you wrote, possibly organized in sub-Folders (e.g. "Top Level VI", "Type Defs", "Sub-VIs", "Globals", etc. as you deem appropriate).
Bob Schor
10-17-2022 03:24 AM
My apologies, Bob. I thought you (and whomever is reading/reads) realized the issue was resolved. I can now successfully move around inside the x-y graph and know where I am.
Here's the solution:
The actual solution is the note I left for myself in the bottom of the case. It wasn't a wrong vi; rather, it was a lack of knowing the checkbox existed. I flipped the state of the box and now I'm good. ...and the above is part of the 2nd event loop.
10-17-2022 10:26 AM - edited 10-17-2022 10:38 AM
@3d0g wrote:
The actual solution is the note I left for myself in the bottom of the case. It wasn't a wrong vi; rather, it was a lack of knowing the checkbox existed. I flipped the state of the box and now I'm good. ...and the above is part of the 2nd event loop.
If that checkbox kludge alone "fixes" your problem, you still have serious dataflow problems and you are just glossing over it. For all practical purpose, you are NOT good!
It is obvious that you don't want our help, even though it could fast-track you with gaining years worth of expertise and experience within days. My offer still stands.