Jump to content

AdamRofer

Members
  • Content Count

    44
  • Joined

  • Last visited

    Never

Everything posted by AdamRofer

  1. Name: XNodes - A Crash Course (PowerPoint) Submitter: LAVA 1.0 Content Submitted: 03 Jul 2009 Category: XNodes LabVIEW Version: Not Applicable Version: 1.0.0 License Type: Creative Commons Attribution 3.0 Potentially make this available on the VI Package Network?: Undecided This was presented at the 02/22/07 LAVA meeting. Discusses the various aspects of both XNodes and External Nodes, shows comparisons, and shows example usage. I ended up skipping over two of the "Creating XNodes" pages since Aitor Solar's XNode Manager is a much better place to create your XNodes with. View the co
  2. 3,414 downloads

    This was presented at the 02/22/07 LAVA meeting. Discusses the various aspects of both XNodes and External Nodes, shows comparisons, and shows example usage. I ended up skipping over two of the "Creating XNodes" pages since Aitor Solar's XNode Manager is a much better place to create your XNodes with. View the comments page
  3. 1,366 downloads

    Copyright © 2006, Adam Rofer All rights reserved. Author: Adam Rofer --see readme file for contact information Description: A couple of Picture datatype hacks to illustrate the structure of the (LV 6.1 - LV 7+ is untested) picture control. -- Main VIs -- Example - Show How Picture Is Made.vi: Main example, shows (incrementally) how a specific picture is generated by displaying the picture with each packet incrementally added. Good way to see how your own pictures display information. Opcodes.csv: Comma-delimited file explicitly describing the packet types and their requirements / u
  4. Name: Picture Hacks Submitter: LAVA 1.0 Content Submitted: 03 Jul 2009 Category: User Interface LabVIEW Version: 6.1 Version: 1.0.1 License Type: Creative Commons Attribution 3.0 Potentially make this available on the VI Package Network?: Undecided Copyright © 2006, Adam Rofer All rights reserved. Author: Adam Rofer --see readme file for contact information Description: A couple of Picture datatype hacks to illustrate the structure of the (LV 6.1 - LV 7+ is untested) picture control. -- Main VIs -- Example - Show How Picture Is Made.vi: Main example, shows (incrementally) how
  5. ABOUT FRIGGING TIME. That is all. Also, XNodes would be good to "release," like other people have said. Even if they need to be "cleaned up" for the "public." - Adam
  6. QUOTE(Aristos Queue @ Aug 3 2007, 12:29 PM) They sure can! Just pop in this bad boy (commence shuddering and fear): http://forums.lavag.org/Recursion-t9832.html' target="_blank">Rusty Nail Use caution with them, though. I am not perfect. NI will provide much more stability in this arena than I will with my rusty nails.
  7. This is a posting of code I haven't touched in a while that seems relevant. This was originally inspired by this forum posting by Norm: http://forums.lavag.org/Automatic-Recursion-t4318.html External Node: http://xnodes.lavag.org/externalnodes/recursion.html XNode (LabVIEW 8.20+): http://xnodes.lavag.org/xnodes/code/AHR_Recurse_xnode.zip This XNode is one that I demonstrated at the User's Group meeting a year ago. It's not tested much, and might need polish, but it seemed to work. Just make sure your VI is re-entrant for it to work. If you want to use the External Node, then make sure to
  8. QUOTE(TobyD @ Dec 28 2007, 01:05 PM) http://en.wikipedia.org/wiki/Degree_symbol QUOTE On Apple Computer's Mac OS, the degree sign can be typed by Option-Shift-8 on most keyboard layouts, including Australian, British, Canadian and U.S. Extended layouts. (Option-K, on the other hand, is "ring above") On Microsoft Windows, the degree sign can be typed by ALT + 0176 on the numeric keypad. On Linux and other Unix-like systems, many keyboard layouts allow typing the degree sign with AltGr+Shift+0. Due to a similar appearance in some fonts in print and on computer screens, some other charact
  9. Easy stuff: 1) Keep code optimized, fewest amount of other apps open, etc etc 2) There's tons of LabVIEW only stuff that you guys should list here that I can't think of 3) Keep your hard drives defragged, registry cleaned, etc etc 4) Get XP SP3 when it is released (assuming it doesn't break anything, who knows yet) -- 10% on average increase in application speed from what people have been saying Mildly advanced fare: 1) Force the application priority AboveNormal/High/RealTime using win32 dll calls (setPriorityClass) or a third-party app that can enforce application priority based on the
  10. QUOTE(jed @ Sep 11 2007, 01:26 PM) I keep a shortcut on my desktop to "C:\WINDOWS\system32\shutdown.exe -a" which aborts any shutdowns that I notice quickly enough. I'm sure a Windows DLL alternative is out there but calling this should work as well.
  11. QUOTE(Aristos Queue @ Apr 30 2007, 02:12 PM) For me, I get: QUOTE Requirements: One of the following is required, please click an item to Purchase. The following membership(s): SIGPLAN Online Membership SIGPLAN Print Membership Sigplan-Fortran Forum
  12. Yes, AQ, I did intend for "new" to refer to "newly discovered." I also figured that Aristotle had not published without some discourse since, but I am always wary of the way of thought that "everything has been discussed" over these topics (or any topics). As the palimpsest uncovering seems to be from Alexander of Aphrodisias (the Wikipedia article needed updating), I thought that a fresh (counter) look from waaay back when this sort of stuff was just beginning to take fruit would be real nice since OOP has been mulled over in completely new context recently. In learning more about the old phi
  13. A new critique on the "object oriented" way of thinking has been uncovered within the Archimedes Palimpsest (article here): QUOTE This refers to Aristotle's Categories. From the article Categorization: "The classical Aristotelian view claims that categories are discrete entities characterized by a set of properties which are shared by their members." And yeah, I know quoting Wikipedia is asking for trouble.
  14. QUOTE(Pablo Bleyer @ Apr 12 2007, 02:03 PM) If you know the type of the control (such as Digital), you can use To More Specific Class and cast it to that strict type...Value then returns the the value in the type that the strict reference has. http://forums.lavag.org/index.php?act=attach&type=post&id=5486''>http://forums.lavag.org/index.php?act=attach&type=post&id=5486'>http://forums.lavag.org/index.php?act=attach&type=post&id=5486 If you don't know how to get a strict reference type, then do this: a) Find the control you want to get the strict reference ty
  15. QUOTE(dsaunders @ Apr 12 2007, 11:06 AM) App.User Interaction:Edit Icon is what you're looking for, just be sure to pass in valid icon data into "Color 256" or else it won't open. Attached VI works in LabVIEW 8.0 (and above, I assume).
  16. QUOTE(mballa @ Apr 12 2007, 08:52 AM) From what I can see, you're stuck with creating your own editor. Use the properties VI.VI Description, VI.Help:Document Tag, and VI.Help:Document Path. Don't forget to save your VI with the method VI.Save.Instrument before closing the reference. Of course, someone else might know how to pop up the LabVIEW VI Properties dialog, but I can't find any methods that do this.
  17. QUOTE(rolfk @ Apr 12 2007, 09:02 AM) The most efficient solution I found (no handle leaks or memory leaks, unlike VISA in LabVIEW 6.1) is to open a reference to the "lpt1" "file" and write to it. This is only used for raw text as far as I am aware, and it's definitely a Windows-only solution, but it works fantastically. No silly CMD stuff is necessary when the Windows API is everything you need. The attached file is written in LabVIEW 6.1 but it will work in all versions. Windows APIs used (pseudocode): Kernel32.dll: handle = CreateFileA("lpt1", GENERIC_WRITE=0x40000000, 0, NULL=0, O
  18. QUOTE(Ami @ Apr 9 2007, 01:46 PM) I gave it a shot and the same crash occurred. It's not like it was intended, but it seems that this functionality isn't available yet. The Add Event Method also doesn't seem to let you specify anything valuable. It seems the EventStructure has the exact same items as a MultiFrameStructure, so there's no special functions exposed with the type. Awesome.
  19. I know the licensing included in LabVIEW 8.0 and beyond has been a show-stopper for some customers. LabVIEW 7 on a computer with the NILM installed seems to be slower, although I don't have any benchmarks to back this up at hand.
  20. QUOTE(Ami @ Apr 7 2007, 05:23 PM) I only have LabVIEW 8.0 in front of me right now, but I found out that casting the Event Structure refnum to a Case Structure refnum and then writing to or reading from the "Frame Names" item crashes LabVIEW (now it's getting fun!). However, writing an array that differs in size with the existing number of Events causes an error 1302: "The size of the array passed in does not match the expected size of the array for the operation." Perhaps this works as of 8.2, 8.2.1, or future versions, but not in LabVIEW 8.0 at least. I'm guessing that "Frame Names" wo
  21. 1000 posts of impressive quality, as well. :thumbup:
  22. AdamRofer

    Macro

    QUOTE(DanyAllard @ Apr 2 2007, 11:51 AM) Thanks for the clarification Dany, I had that set from before so I forgot it was necessary. What happens when you drag the .vim from explorer onto a Block Diagram?
  23. AdamRofer

    Macro

    QUOTE(Aitor Solar @ Apr 1 2007, 10:55 PM) I'm not sure how far back this goes (probably as far back as the Macroizer thing exists), but this VI appears to run in one instance. Apparently you can have an automatic "macroization" of any VI you want. (This was tested in LabVIEW 8.20) Step one: take a VI "xx.vi", rename it "xx.vim" Step two: drag it onto the block diagram Now this VI is a subVI, but note you cannot double click on it to enter the VI itself. I imagine that all the other problems that plague External Nodes in general exist here also, which might be why this behavior is not a
  24. QUOTE(Gavin Burnell @ Mar 29 2007, 01:37 PM) I started off that way to try to find an answer to your question, and it tells you that it's a Node (surprise!). You can typecast a similar object to acquire a similar function that isn't necessarily exposed on that object, as Yen pointed out in this forum post: http://forums.lavag.org/How-to-get-reference-to-Text-of-StringConstant-t5791.html' target="_blank">How to get reference to Text of StringConstant? I couldn't get any probable casts to work, I thought Formula.Formula Expression would be the closest match. Decoration.Text.Vertical A
  25. QUOTE(i2c @ Mar 25 2007, 03:23 PM) I have used quite a few ActiveX components in LabVIEW and I've discovered a few things over time: 1) In LabVIEW, always close your references; always close your references. Always close your references. If you don't then bad things might happen, like random hangs. 2) Variables (such as the TimeStamp in LV 7+, aka Date in VB6) don't always match up perfectly, so experiment before releasing stuff to other people. 3) Any problems in your ActiveX component (memory leaks, handle leaks) will still exist, so make sure you don't open a reference to a registry
×
×
  • Create New...

Important Information

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