Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/19/2015 in all areas

  1. Hi LAVAers. I thought I'd post this up to grab some more eyes and ideas, and maybe contributors if there is interest. I've started development of an open source datagridview project using .NET in LabVIEW to finally have a well implemented datagrid for use with LabVIEW UIs, data types and event integration. I have this all working in a sample project and would love more ideas, feedback and and help if anyone wants to contribute. The project is hosted on github, https://github.com/unipsycho/LabVIEWdotNetDataGrid I started a discussion for it in the LabVIEW NI community site when I started but its a LOT more presentable now, so extending this to LAVA. The original discussion is here: https://forums.ni.com/t5/LabVIEW/OpenSource-Project-for-a-NET-Datagrid-for-LabVIEW/m-p/3194273 The main premise of the project is to have extended data types, extended features with a event driven datagrid for LabVIEW using .NET. Please let me know what you think or if any questions or ideas to add to this.
    1 point
  2. I’m more going for SER, Signal-to-Effort Ratio, at the moment as I have limited time to spend on things like editing. Something is better than nothing. And a programming instructional video that doesn’t drag is a pretty high bar (not sure I’ve seen many of those!).
    1 point
  3. These are great, but they tend to drag on a bit too much. I would suggest considering either editing or planning them carefully enough so that you have a higher SNR. For instance, the third video has a good explanation of the value of relabeling messages, but it comes after a pretty long video. Also, you might wish to start with a video about the basics of the framework. As it is currently, it focuses a lot on actors and less on messengers.
    1 point
  4. Have you considered making it an XControl so it is a drop in replacement?
    1 point
×
×
  • Create New...

Important Information

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