-
Posts
6,196 -
Joined
-
Last visited
-
Days Won
104
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by Michael Aivaliotis
-
-
Could you do a quick video demo of what this thing does and post it up here? You can use Jing. It's free.
-
There's no such thing as "free time". All time is the same. You decide how to slice it up.
-
resolvd.
-
Am I suppose to be able to drag and drop from a browser to my diagram? Can't seem to do it. I'm using Chrome.
-
-
-
I use methods and properties on the diagram all the time. However, I also use clusters or arrays of ctrl references passed into subVIs as well.
I don't think it's a good idea to manipulate UI objects from within a class unless the main purpose of that class is to manipulate the UI. Like a UI class.
In your example, I would create a method called Engine State. I would read that state, and if the engine was running, I would disable the button.
- 1
-
So I made a small tweak that should fix this issue. Moving forward. If anyone sees this again please post here so I can dig deeper (that's what she said!).
-
I think it is very annoying the handle these front panel items in my top level vi block diagram.
Why is it annoying? What is your goal?
-
I've seen it a few times too. Fairly random "feature"
Just need to up the PHP memory limit a bit (I bet it's set to 32MB)
Ya, I'm aware of this. On my radar.
-
Just want to give an update that we've moved this to the LAVA CR. That way, it's easier to do revision updates. And it gives better visibility.
Also, there is a new version. That was just posted.
-
Solving this issue is as pleasurable to me as a root canal...
-
What are these 2 files? Your own custom files or part of LabVIEW run-time?
-
Is your laptop connected to the same internet service provider your desktop is?
-
Am I missing something or is it some problem with the site?
How can I resolve this problem?
The issue has been resolved. Please try uploading your code again.
-
-
Thanks for letting us know. Will look into it.
-
I might be missing something, but those examples seem to demonstrate the Factory Pattern but do not address the messaging problem I am trying to solve.
Really? Did you open up the code?
They are also referenced here:
http://decibel.ni.co.../docs/DOC-12645
I don't think it's an exact match to your proposed solution but it has the right elements.
-
See here:
http://decibel.ni.co.../docs/DOC-15014
Specifically look at the UI Framework code.
I think it kinda does what you are asking. Each message is a child class.
This presentation was given at the CLA summit this year.
I am very interested in this design pattern as well.
-
I'm glad it all worked out.
-
Is anyone else having issues accessing LAVA?
-
Ok, now I have a new problem that comes under the topic heading. The file uploader is failing to upload my files... I select the file on my computer, I get the progress bar and then it comes to the end saying that the upload failed. I've tried Firefox and IE8 and also checked that it doesn't make a difference whether I access the local file via system Library or direct path (Win 7 64bit). So now I'm a bit stumped for ideas.
Please try now. It's fixed. There was a glitch due to the recent server upgrade.
-
-
What version of LabVIEW did you upgrade your current LabVIEW application from? I assume it was working before (on the previous LV version) and now it's not working?
How are you testing this on older LV versions? Are you down-saving the VIs?
When you say the DLL returns all the correct info. How is that possible if it cannot communicate with the hardware? What is returned?
How to call a plug-in object from an executable?
in Application Builder, Installers and code distribution
Posted
I would think that source distribution is your best bet. If you don't like the detailed hierarchy then you may use llb as your destination. You can put each class into separate llbs.
If you want to use the EXE method that I think you would need to run the EXEs and communicate to them with an application reference mechanism and VI server calls. Not sure what you did exactly in the EXE implementation.