Jump to content

LAVA 1.0 Content

Members
  • Posts

    2,739
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by LAVA 1.0 Content

  1. QUOTE (mesmith @ Feb 5 2009, 03:16 PM) That is no problem, this is all done in compile time (the name of the event is part of the 'wire'). Ton
  2. QUOTE (GraemeJ @ Feb 5 2009, 01:21 AM) Face it, the user has one FP, so one event structure for FP events will be fine. The processing could be done in consumer loops. Ton
  3. The easiest method is to adjust the display format of the numeric to Relative time HH:MM:SS: Ton
  4. You started a so called 'Category' page. This special page is like an index to all pages that contain the [[Category:xxxx]] tag. Your page is located at Application_instance, I added the page to the Category:Application_Control. Ton
  5. QUOTE (Michael Aivaliotis @ Feb 2 2009, 08:54 AM) The wiki editor is localized :thumbup: Ton
  6. Here is a VI to get the 'friends timeline' of some user: </p> There are some dependencies: -JKI XML toolkit -OpenG picture Toolkit -NI Internet Toolkit (for getting the user image) Apart from the XML toolkit those should be quite easy to bypass. Download File:post-2399-1233427687.llb Ton<p>
  7. Lately Volbeat, or Joel Spolsky and Jeff Atwood discussing programming. Both very inspiring Ton
  8. QUOTE (Michael_Aivaliotis @ Jan 30 2009, 01:42 PM) I'll probably plan to add a few more functions before submitting it.
  9. QUOTE (PaulG. @ Jan 30 2009, 09:59 AM) Same idea as Paul G, but write the time of the first run into the registry (assuming you are running on Windows). Every time the application starts, check the registry location. If the entry is not there you assume that it is the first run and you write the time/date to the registry. If the entry is already there then check to see how much time has passed, and if it is more than 15 days, exit the application. To make the registry entry harder to find manually, do not use an obvious name for the key and encode the value (time/date) using some simple algorithm.
  10. The attached VI is a simple example showing how to update your status on Twitter from within LabVIEW. You could use it to send updates, measurements, status information or alarms from your application. Note that Twitter limits the number of updates per hour that it allows. Download File:post-3370-1233292805.vi Download File:post-3370-1233292798.vi
  11. QUOTE (Maca @ Jan 30 2009, 12:54 AM) QUOTE (crelf @ Jan 30 2009, 01:32 AM) Easy! Buy a premium membership LAVA: The spam supported community. Ton
  12. QUOTE (crelf @ Jan 29 2009, 10:05 PM) Yep, I get what you want. I don't think this can be done in a truly fully generic way programmitically. The routine 'Right Click->Advanced->Customize->{(Strict)TypeDef}->Save' is what you need. I've got a feeling that this is not possible. One could write xml/ini based solutions but they are tight to control types. Would make a wonderful class routine. Ton PS, learn how to ask questions on twitter in 160 characters...your initial question seemed so much simpler
  13. Non-Premium members are allowed to sent 10 PM's per day. I am not sure if this is technically possible. (See here) Ton
  14. Another patch might be: Non-Premium members are allowed to sent 10 PM's per day Ton
  15. QUOTE (Antoine Châlons @ Jan 29 2009, 08:31 PM) Antoine, I just send you the spam message. Ton
  16. ok, i just read on this page: http://www.dotnet247.com/247reference/msgs/57/285549.aspx that Control.FromHandle only works on windows in the current process (for .NET). Now the .NET code that you call should be running in a different process than your LabVIEW process, so Windows Security finally takes effect.... I guess we may have to do this the old-fashioned way - with windows hooks. I will have to do some reading first for this one. My app had all its windows running in the same process, but apparently that is not the case for LabVIEW. Take a look at this NI example: http://zone.ni.com/devzone/cda/epd/p/id/4394 You want to intercept messages that go into your LabVIEW window, and you want to listen for the WM_MOVE message. (Too bad we can't do this in .NET) anyway, have to go get some food now.
  17. This is what I came to conclude: The int to IntPtr VI works perfectly fine, I verified this by getting the actual handle to my window by using Winspector, and by calling the "ToInt()" function of the resultant IntPtr .NET object. Now, after calling the Control.FromHandle function, I tried accessing any property of the resultant .NET object (of type Control), and none of the properties were coming back! I fear this may be because of some sort of Security feature of .NET. I will try to replicate this similar behavior on my computer by creating a non-.NET (aka unmanaged) C++ program that would represent LabVIEW, and then call the same .NET functions. Real quick, what version of .NET are you running? Another thing we can do is to write our own custom .NET Assembly that would implement the desired behavior and to then call our own custom .NET Assembly to do what we want.
  18. QUOTE (vultac @ Jan 28 2009, 11:26 PM) Try to get your hands on the NI State Diagram Toolkit (not the statechart module). It is obsolete but perfect for what you want. Another (good) option is using a statue machine, for instance the JKI statemachine (after how many plugs do I get a VIPM license?) Ton
  19. Your handle appears to be fine, you can always verify by using: http://www.windows-spy.com/download/ i am playing around with your code right now.... looks very nice
  20. I just saw something quite interesting in the MSDN.... You can easily hook into the events of another window/form/control by using the Control.FromHandle(IntPtr Handle) static member to create a new Control type. All you need is the window Handle, see if LabVIEW exposes that for you, otherwise we will have to look for an alternative way of retrieving it. private static IntPtr _handle = IntPtr.Zero; static void MyThread() { Control testForm = Control.FromHandle(_handle); testForm.Move += testForm_Move; } static void testForm_Move(object sender, EventArgs e) { Control myControl = (Control) sender; System.Diagnostics.Debug.WriteLine("Location: " + myControl.Location + ", Size: " + myControl.Size); } So what you have to do from LabVIEW is call the .NET 2.0 static method "Control.FromHandle(IntPtr)", and then you have to listen to its "Move" event. (http://zone.ni.com/reference/en-XX/help/37..._hndl_ax_evnts/) Each Move event callback will have a sender parameter which is simply the Control object, and once you cast it to Control you can get that windows properties. I am attaching a Visual Studio .NET 2005 C# solution with this example. (I do not have LabVIEW installed here but I can do it when I get home)
  21. Is this what you are trying to do: Display: Show a main window Show one or more child windows relative to main window Event Responses: Whenever the main window moves, you want each child window to follow the main window with a certain offset. Whenever one or more child windows move, you want the parent window to move the same way. (I guess you are looking for behavior similar to WinAmp 3.0? where your playlist would snap to the player...etc) Well, I have done something very similar - and many people like to call it "snapping". Basically what I did was start sniffing the Windows Messages of the main window from each child window, and whenever a move was detected I would set a local boolean variable to "true", and move that corresponding child window. And the boolean variable would disable the sniffing of windows messages until the move was finished. And I did the opposite for the main window listening to each child window. This shouldn't scare you to implement in LabVIEW, but I do recommend using an iterative approach, let me know if this is what you intend to do.
  22. QUOTE (NeilA @ Jan 28 2009, 06:39 PM) QUOTE (normandinf @ Jan 28 2009, 06:56 PM) There are many properties and methods to allow you to control exactly what you're describing. Check out these to start: VI.FrontPanel.Open (Property node) VI.RunVI (Method) And I suggest you command the spawned VI with Queues or Notifiers (to instruct it to close for example...) And VI.Abort (method). Pausing a VI is afaik not possible. Ton
  23. QUOTE (Michael_Aivaliotis @ Jan 26 2009, 11:56 PM) And while you are at it. The Wiki button is gone from the Quick Access. Ton
  24. Maybe any of the Private events? Especially VI Redraw and VI Scroll, I think VI Redraw is the one you should study. Ton
×
×
  • Create New...

Important Information

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