Jump to content

Aitor Solar

Members
  • Content Count

    259
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Aitor Solar

  1. You can close the FP with an explicit reference to itself, that way wou won't be prompted. I mean: Hope that helps. Saludos, Aitor
  2. QUOTE(Felipelc @ Jan 15 2008, 07:12 PM) Yes, though is not immediate. When the user selects the new color set, you'll have to change the colors of all the affected elements through property nodes. Saludos, Aitor
  3. QUOTE(guruthilak@yahoo.com @ Jan 8 2008, 05:16 AM) As already said, here you'll find a couple of tools: http://forums.lavag.org/Scripting-Workbench-Beta-t9518.html Saludos, Aitor
  4. QUOTE(Saverio @ Jan 4 2008, 05:23 PM) Did you changed the code of a .vi file? And doesn't LabVIEW return something as "corrupt VI" or similar? Saludos, Aitor
  5. QUOTE(tcplomp @ Dec 19 2007, 10:53 AM) Well, the "Open VI Object Reference" function is inside LabVIEW, though is not shown in the palette. That OpenG package "just" gives an easy way of placing it in the block diagram . Saludos, Aitor
  6. Yes, it seems you have to access specifically through the container pane: Maybe it's easier to access to it through the block diagram: Both work. Saludos, Aitor
  7. QUOTE(Gavin Burnell @ Dec 15 2007, 02:50 PM) Of course it's possible, my XNode does it: Download File:post-1450-1198053874.avi But when you have a strict VI reference the VI is reserved, so you usually can't use the run method (more tricks needed to do it), and so the XNode usefulness is reduced, hence I didn't mention this possibility. QUOTE(Gavin Burnell @ Dec 15 2007, 02:50 PM) Are you planning to release your XNode on the Lava CR ? Not now, it has a lot of dependencies . But I can pass it to test, send me a message if you want. Saludos, Aitor
  8. QUOTE(Gustavo Fernandes @ Dec 18 2007, 04:30 PM) Search for "COM Builder" in the MathWorks site, there are a lot of examples, and for modern versions look into the .NET Builder: http://www.mathworks.com/products/netbuilder/ Saludos, Aitor
  9. What Tomi said, maybe you're using a non-creatable object. You can also generate your own COM object from Matlab to encapsulate the methods you want to use from LabVIEW. Saludos, Aitor
  10. QUOTE(phuzionz @ Dec 18 2007, 09:54 AM) Do you mean this? http://lavag.org/old_files/monthly_12_2007/post-1450-1197971757.jpg' target="_blank"> EDIT: Oh, programmatically. That would be scripting, try the "Add Frame" method and the "Frame Names" property for CaseStructure class. Saludos, Aitor
  11. I also prefer the first method (call me traditional ). To avoid the necesity of writing down the controls' names (so error-prone), I have developed an XNode to manage the Set Value and Get Value methods automatically. Visually is similar to the Call-By-Reference function, and you can easily drag a VI or browse to the desired VI: The XNode's generated code just gets and sets the connected values: Next step is to automatically update the XNode pattern when the referenced VI changes, but Aristos warning about linker functions has frightened me . Saludos, Aitor
  12. 3D Picture Control just doesn't work in remote panels. The screen remains black and nothing is shown. CAR 46F27J15 Saludos, Aitor
  13. QUOTE(Tomi Maila @ Dec 1 2007, 11:22 PM) I think you are triying to do this, don't you? This avoids the "VI is not in a state compatible with this operation" error. http://lavag.org/old_files/monthly_12_2007/post-1450-1196669259.jpg' target="_blank"> Saludos, Aitor
  14. QUOTE(Tomi Maila @ Nov 30 2007, 03:25 PM) Maybe you are using the Fake Execution State method? Saludos, Aitor
  15. QUOTE(Phantom Lord @ Nov 20 2007, 01:35 PM) Create a local and test it in every iteration. See the attached VI. Saludos, Aitor
  16. I addition to what Ton said, in the code you're not breaking the inner while loops. I'm not sure what's your goal, so: 1) If you want to check from an inner loop if the stop button have been pressed, you can use a local. 2) If you want to check from a running subVI if the stop button have been pressed, you can use the reference, but is probably better to implement some kind of communication as queues. Hope that helps. Saludos, Aitor
  17. QUOTE(tcplomp @ Nov 20 2007, 11:19 AM) All right, is a shortcut to File -> VI Properties. You know, I always use a right-click on the VI icon and then "VI properties" and that doesn't work with polymorphics. Thanks, Ton. I fell stupid now Saludos, Aitor
  18. The stop command should be detected even if there are subVIs (but the loop won't stop till the end of the iteration). Could you post the code, in a simplified form? BTW, in LV85 you can stop a for-loop too. Saludos, Aitor
  19. Adding a description to a polymorphic VI should be obvious but... well... I can't find it. I've been doing it through the poly VI reference, but sure there is an easier way, isn't it? Saludos, Aitor
  20. Aitor Solar

    ?

    QUOTE(M.M.K @ Nov 18 2007, 10:47 AM) Because i goes from 0 to N-1, so your last iteration output is MAX - INC. Add a +1 to the N or to the i. Keep also in mind that you are casting a double to an int when you set the N value; you have no guarantee the selected increment can reach the max value (for example, if MIN=0, MAX=1 and Increment=0.3, you won't reach 1 but 0.9 or 1.2, depending on the N value). Saludos, Aitor
  21. QUOTE(Michael_Aivaliotis @ Nov 15 2007, 09:49 AM) But I'm afraid you are still alone in the "detachable node" club . I was going to explain how I did it, but I don't want to take away your well-earned NIweek beers . Saludos, Aitor
  22. QUOTE(martin@aerodynamics @ Nov 14 2007, 12:30 PM) Error 1077 is usually associated to a wrong property name. Are you sure all the German names you put are correct? QUOTE(Tomi Maila @ Nov 14 2007, 03:13 PM) 1) Regular expression filtering of class hierarchy while typing into a search field (see Draw Hierarchy.vi and Filter Hierarchy.vi in my tool) 2) Regular expression filtering of methods and properties while typing into a search field (See Filter Items.vi in my tool) Yes, the search capability should be heavily improved. I like the approach of your tool, though I still like a global search function because sometimes you just don't know where to look. I also left out the possibility of creating constants, something your tool has. It was for the sake of simplicity, since you can create a constant from any property ot method, but in fact the question is more complicated if we include strict constants. It happens some classes (like the Vision Image Display) are in fact a strict sub-type of another class, allowing properties and methods the original (un-strict) class doesn't have. But for now I don't see the point of digging that way. QUOTE(Tomi Maila @ Nov 14 2007, 03:13 PM) 3) Ability to automatically "reverse engineer" classes, properties and methods for new LabVIEW versions when the tool is started in a LabVIEW version for which there is not yet configuration files generated (I've not implemented this so...) Umm, do you mean the tool should automatically find all the possible classes, properties and methods? I'm afraid that's not an easy task and is far beyond the scope of this simple tool. Generation of the classes tree can be automatic (and fast) through scripting, but usually crashes labview. Finding the correct properties and methods names is more difficult and I prefer not to elaborate on that. I don't know if you have find an immediate way for recovering all that info, I haven't . QUOTE(Tomi Maila @ Nov 14 2007, 03:13 PM) You can also make the start-up faster by using VIs as configuration files. You know how to script a VI with certain default values on the front panel indicators. Such VIs can function as very fast and extensible configuration files. Simply either 1) open the VI and read the front panel controls or 2) open a reference to the VI and call it dynamically. The latter method is faster but requires a little more work if connector pane is changed as old connector pane formats need to be supported. Well, the startup seems really fast for me but, I have understood correctly, with the approach you propose, for adding or changing a property would be necessary to open the VI, change the value and making it the default value. I thing the txt files are much more versatile and user-configurable. Saludos, Aitor
  23. Well, well, well, it seems really easy when you know how Saludos, Aitor
  24. QUOTE(martin@aerodynamics @ Nov 13 2007, 10:39 AM) Umm. Open "update property.vi" and "update method.vi" and change the "VI Server:" text in both, since probably is also different in German. Follow the image guideline: http://lavag.org/old_files/monthly_11_2007/post-1450-1194956768.jpg' target="_blank"> Saludos, Aitor
  25. QUOTE(dannyt @ Nov 12 2007, 01:07 PM) Sure, here it is, try it. Keep in mind that this just replaces the llb, you'll still need the directories provided with the first zip. Saludos, Aitor
×
×
  • Create New...

Important Information

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