Jump to content

Aitor Solar

Members
  • Content Count

    259
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Aitor Solar

  1. I have to enable / disable / hide a control. Easy, isn't it? Property node -> visible or disabled. But the VI is going to be seen in a remote panel, and in RPs (in a net with big latency, to add) property nodes are really (I mean reaaally) slow. I can't use them. What can I do? The only idea I've had is to use a tab control. Tab 1 has the control, tab 2 has nothing, a change in the tab value is almost inmediate. But this doesn't reproduce a "disabled" behaviour, just invisibility. I'm stuck there. A tab page can be invisible, but then you see what's under the tab control, not what's in an
  2. I have changed it to work with all colors (a tiny modification: RGB goes to BGR). Saludos, Aitor Download File:post-1450-1150103890.vi
  3. Now, what I haven't discovered is how to give control programmatically to a specific client that's viewing the VI. This can be done from the client machine (either right-clicking, or from the local LV through the Request Control method). But if the client just has the runtime and it's viewing the RP through a web browser, you can't give him the control from the server machine, just unlock the panel and wait the human user to ask for it :-(. Saludos, Aitor
  4. It would be great, but how? OpenOffice has an ActiveX control, but not a server, I believe. So, communication would be a problem. Saludos, Aitor
  5. I haven't seen your code since I don't have LV8 in this machine, but basically you have two ways, AFAIK, depending on the specifics: 1) Open a VI reference to "power panel" from "power interrupt" and get a reference to the control you want. Use then the "value (signaling)" property node to trigger a "Value change" event in "power panel". 2) Register dinamically events from "power interrupt" in "power panel" through a "Register for events" node. But from your description, I think this method is not what you're looking for, because it only registers events, not program actions. Saludos, Aito
  6. They work in 7.1, but not in 8. Saludos, Aitor
  7. Probably a port conflict, I'd say. Create a simple html file (called for example "hi.htm") in the web server root directory, let's say something as simple as: <HTML> <BODY> Hi! </BODY> </HTML> Open the browser and go to localhost with the selected port, i.e.: "127.0.0.1:3333/hi.htm" (because, as you have seen, opening directly from windows leads to an error in the remote panel, 'cause you're not entering through the server). You should see the "hi!" message. If not, try using another port. First, check the web server is running, disable proxys, etc. Saludos, Ait
  8. IIRC, reports had a method to print them in the default printer. Not a lot of options, but it worked. VIs can also be printed. To anything more complex than that, follow jpdrolet recommendation. Saludos, Aitor
  9. OK, have you tried "TCP Open Connection"? What kind of error do you get? Saludos, Aitor
  10. Maybe I'm being too obvious, but does the ping work? Saludos, Aitor
  11. If you just want to change the images once and forever, you can try the customize advanced option. If dinamically, an Xcontrol could be the answer (or even a picture, controlling its events). Now I can't remember a way of doing it with a script, and even it there's one, using it could be problem-prone, as all copies of that ctl would change, etc. Saludos, Aitor
  12. You can check if the file already exists (in fact, the file dialog tells you), and in that case delete it before proceed. Saludos, Aitor
  13. Well, I re-installed LabVIEW and I have managed to communicate between exes through a shared variable with no problem at all. I suppose something was bad with the previous installation Saludos, Aitor
  14. Open in Default Browser uses DDE to pass a "WWW_OpenURL" command to the default browser defined in Windows register, and if that fails it uses a System Exec call to the browser executable. Depending on the browser you are using, you can add other parameters to WWW_OpenURL, as WindowID to specify the target window, or use other commands to create a new window and then open an URL in that. Otherwise, you usually (Firefox, Mozilla...) can define the browser behavior referring to urls coming from external applications, so it launches them in a new window / tab. Saludos, Aitor P.S.: Oh, and of c
  15. I have observed xcontrols lack unit label (or, at least, I haven't be able to find it), so you can not wire the xcontrol to a wire that has units . OK, the unit is defined in the data type in Data.ctl, but I can't see any way of modifying it programmatically. Opening it from the fa
  16. With so much information as you provide, the answer should be "probably not". It depends on what you're doing in that script. But you have the "Matlab script node" in LabVIEW to import it (take note you still need Matlab installed in the machine). Saludos, Aitor
  17. The VI works right for me, provided I change local address to 127.0.0.1. I haven't studied the code, but the basic advice would be to check your net settings and be sure the listener is created and ready before the client connects. Saludos, Aitor
  18. I don't think it's so hard, in fact. You have an example in LabVIEW (Help -> Find Example -> Communicating with external application -> Excel) and the library it uses. All is based in opening an Excel ActiveX object and operating its methods and properties. Saludos, Aitor
  19. No, neither the warning text. I think it wouldn't be difficult, but would add more properties and my aim was a code as simple as could be ;-). Saludos, Aitor
  20. Here's my code. Probably is not a pure quine, since it copies its own diagram, but I like it as a proof of concept of simple self-reproducing code. Surely it's possible to improve it a lot of ways . Saludos, Aitor Download File:post-1450-1147293434.vi
  21. But what would be considered a quine in LabVIEW? In text languages, usually such a program has a string output that contains its code. But in LV, that's not possible (I think). I have developed a VI who creates a new VI with its same code. Does that count? What's my prize? I'm not sure. It would be a pity some day we should start quarantining all VIs to be sure they have no malign code. On the other hand, the tools are there, easily available to everybody. And when scripting licenses become available, the possibilities will grow much further (documentation, access to all functions and obje
  22. Of course, you can easily destroy almost everything in the computer or even copy a VI a million times. But I think this is more subtly. The code keeps copying itself inside other VIs diagram without destroying their original purpose, and so each infected VI acts as a new propagation point. And you could hide the code, for example, in an invisible (or not immediately visible) zone, such as inside a frame, behind something, etc. So it's possible that, after some time, you discover all the VIs in your application (even most LabVIEW VIs) have been infected, retarding the execution and forcing you
  23. Hi, people. I've been rummaging through this idea and I have managed to create a piece of self-reproducing code (I have to admit it's no difficult). It copies it's own code in other VIs, then when those VIs execute, they copy that code in others, etc. As a concept I find it fascinating, but it's a little nasty if you aren't careful. So, does scripting suppose a new danger to free VI sharing, like in forums? What do you think? Probably this is one reason NI doesn't want people playing too much with these new tools. Maybe in a few years we'll need antivirus for LabVIEW . Saludos, Aitor Oh,
  24. I don't understand what do you refer to with "the VI server case with shared variables", I considered them two different ways of transmitting data. Or do you mean affecting shared variables through VI server? I hadn't thought about that, but it would sound interesting (if you hadn't already stated that won't work, of course ;-)). About the crash, I really don't know, the laptop just crashed repeatedly when the "deploy" window appeared. I'll try to test it in another machine, if the license allows me to do so. Saludos, Aitor
  25. If you are talking about remote panels (i.e.: see and control remotely a LabVIEW program through a web browser), you just need to add some lines of code to the HTML file, you don't need Frontpage or any special program. But, as usually, I'm not sure if that's what you're asking. Saludos, Aitor
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.