Jump to content

i2dx

Members
  • Content Count

    681
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by i2dx

  1. I stumbled uppon this issue, too, some time ago, and finally I kept the code, that generated the menus dynamically. If you don't use H U G E right click menus, there is no recognizable performance loss. I've tested that with 40-50 menu items (which were created dynamically themselfes, depending on the item you clicked on) and did not recognize any delay gl&hf cb
  2. are we fighting? oops ... sorry guys, my english is not that good that I would recognize the fine nuances. I only understand the technical terms and "hidden intentions" if they are obvious ... but if you want to blame me for that, just do it, I'm used to it ok, back to topic: I don't think that using references of the controls of a user interface adds "more" decoupling than using e.g. an event strukcture, because in the end you have to write code, that handles all that user interactions, and if youi don't use an event structure, you'll have to write all that code on your own. OK, you gain
  3. yepp. that structure you describe is called a "distributed software". I'm writing a lot of this type of code: the "work" is done on a RT-System, the user-interface (I call it "Client") is running on a Windows system. In that case I use the TCP-Messages, I send to the "server" like an event. In fact it is an event - e.g. a pressed button. The only difference is: the "messages" that go directy into the state-machine in the example above are wrapped into a TCP-packet, sent to the server, unwrapped and put into the state-machine on the RT-server ... so the only difference is the method of transpor
  4. maybe I totally misunderstood the question / discussion, but why are you all talking about using control references when decoupling the UI from the Code? I simply use this pattern: The upper state machine handles all the FP events (button pressed, value changed, etc ...) and the statemachine below does all the work. In the user-event state also handles all the dialogs, etc. - all that stuff that blocks FP actions - and you can use the user-event case, too, do send messages back from the lower state-machine to the event handler (e.g. to disable buttons, set values to controls, etc ...) If
  5. yea, 7.1.1 was great. OK there was no project explorer (and I could not imagine working on big distributed systems without it!), working with an FPGA was somewhat "tricky" and if you wanted to work on an RT-Target and a Windows-Target at the same time, you had to use some really dirty tricks, so many of the features in the current versions are really improving my day to day work! But on the other hand: almost all features in LV 7.1.1 I used in my daily work were working properly and that's what I'd like to see again. And if that would mean that there are less features or no new features at all
  6. this is the right thread for me to drop a few lines most of the stuff posted on that "I hate LabVIEW page" is pure bullsh**! Those guys simply should do a Basics I + II course or read a book like "LabVIEW for Newbies" or something like that and most of their "problems" would be gone. If the don't understand how to use LabVIEW and how it works, it's not the failure of the Tool or NI, it's their fault. If I read things like: I'd like to answer: why don't you stupid use the VI Documentation? and why don't you use the text-tool in the BD? --> have you ever heard about the text-tool? Yo
  7. if I am allowed to say this: giving official statements once per year to the users reminds me much more of the german bureaucracy then a modern customer feedback system
  8. with my kudo, the counter has now reached 250 ... still 50 to go that's exactly how I use the idea exchange: I visit about once per month and kudo all the new ideas I like ... I would not use that, because that would be information overflow - for my taste ...
  9. if you loose the connection (by whatever reason) you have to close the connection on both sides, using the TCP Close primitive. Then you have to open a new listener on the server side and connect again on the client side and maybe you want to give both sides a little wait time to allow the TCP-Stack to call it's clean up routines (50 ms shuold do ...). The client recieves an error 66 when the server closes the connection (e.g. due to an error), you have to handle that one and just ignore error 56, if the server as not jet sent data ... I'm using the Simple TCP Messaging protocol since years
  10. yea! I like the function of my micro-wave, too! (really!)
  11. I don't think the logo should look to much like a BD. LAVA is the Front panel of the LV-Community (because we are talking in the bright light of the general public here ) not the hidden block diagram i like it!
  12. i2dx

    PXI advantage

    no. MXI is more or less "just" a extension of the PCI-Bus of your host-system. If you want a OS on your PXI (and write RealTime applications) you need a controler.
  13. congratulations! and just because I just read it: thanks AQ for writing C++ - so I don't have to do that! (that was really pain in the - you know where)
  14. 1,288 downloads

    Author: Christian Berger --see readme file for contact information Description 1. What is this tool good for? This tool was made to set front panel properties in LabVIEW 8.20 programmatically. You can define in a text-comment how the front panel should look like, place this comment in the block-diagram and let the tool do the rest 2. Why was this tool made? I have created this tool, for one main reason: Sometimes it's annoying to debug running code, if you have dialogs with the FP properties "open when called" and "modal" set. With this tool you can define, how the FP should look lik
  15. File Name: IBB Frontpanel Tool File Submitter: LAVA 1.0 Content File Submitted: 02 Jul 2009 File Category: LabVIEW IDE LabVIEW Version: 8.2 File Version: 2.0.5 License Type: GNU Public Potentially make this file available on the VI Package Network?: Undecided Author: Christian Berger --see readme file for contact information Description 1. What is this tool good for? This tool was made to set front panel properties in LabVIEW 8.20 programmatically. You can define in a text-comment how the front panel should look like, place this comment in the block-diagram and let the tool do t
  16. 1,298 downloads

    Project Copy Tool (LV 8.0.x) V1.3.2 Copyright © 2006, i2dx All rights reserved. Author: i2dx --see readme file for contact information. Description:: Purpose: copy a complete VI-Hierarchy of a Project to a new directory starting with the TopLevel VI ... it works quite good with my projects, and i hope you will find it usefull. please report bugs, if you use it! Features: it builds the complete vi-hierarchy starting at the top-level vi it extracts VIs which are bound to lvlibs when copying to the new folder it replaces Project - prefixes (i work with project prefixes ...) eg. BMW_MT
  17. File Name: Project Copy Tool File Submitter: LAVA 1.0 Content File Submitted: 02 Jul 2009 File Category: LabVIEW IDE LabVIEW Version: 8.0 File Version: 1.3.2 License Type: GNU Public Potentially make this file available on the VI Package Network?: Undecided Project Copy Tool (LV 8.0.x) V1.3.2 Copyright © 2006, i2dx All rights reserved. Author: i2dx --see readme file for contact information. Description:: Purpose: copy a complete VI-Hierarchy of a Project to a new directory starting with the TopLevel VI ... it works quite good with my projects, and i hope you will find it useful
  18. i2dx

    Alfa Oddness

    there is a little devil sitting on my shoulder and whispering in my ear: Alfa is not an individual, it's a group of scientist (psychologists ?) who do some practical research how a social group of more or less intelligent individuals is responding to absolute nonsense input in their Internet "living-room" => we are somewhat like their "test animals" but who knows?
  19. QUOTE (lavezza @ Jun 5 2009, 10:56 PM) no, but the ini-key that relveals the private property and invoke nodes is still working ...
  20. QUOTE (crelf @ Jun 1 2009, 05:21 PM) ACK! But now I can go further: generate a new VI from a Template VI and automatically adapt it with scripting to my "project needs", which will in fact reduce my template jungle and I can create my new templates more generally
  21. QUOTE (Aristos Queue @ May 30 2009, 06:26 PM) uhm, I read your initial post somewhat in a way that YOU were lobbying and YES, I know it's dangerous. But fire is dangerous, too - but can you imagine a BBQ without it? And if you don't believe me, you are invited to come down to Ft. Myers Beach, then I'll show you . Finally I am now again able to waste lots of hours to automate a programming task which could be done with templates much quicker - or, just to express this in a more positive way: I can quit my WoW account and start developing tools again QUOTE (Aristos Queue @ May 30 2009
  22. QUOTE (James Beleau @ May 29 2009, 09:21 PM) Although I never have tried this with mySQL I think it should work, if you pass the data as plain string (use the flatten to string primitive e.g.). You should read the mySQL documentation and find out what the "special characters" of the DB-Server are, which need to be "escaped" in the SQL-Statement. I assume that you need to insert a large amount of data, because you use a BLOB field? If not, and the data size is about "a few kilobytes" you could use a trick and convert the binary data to a string, then to an u8 array and the u8 array to a he
  23. This wish has beend posted several times before, and the answer was always: we can't do this, because there is no way to connect controls to a wire at runtime (e.g. because there is no block diagram at runtime ...). My assumption is: even with the newly released scripting there is no way because scripting will not work at runtime, just at development time. Unless this task is easy to do in other programming languages, it will be hard to archive in LV, because IMHO this would require something like Objects by reference (in the C++ or C# sense of Object)
×
×
  • Create New...

Important Information

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