Leaderboard

This isn't related to EULAs or LabVIEW FPGA, but you might like this site: http://tosdr.org/

Some of the details of adding new control types was posted in the other thread, but I'd really like it to be class based with dynamic dispatch. At the moment it is a bit of a pain to add new types but clearly is possible. Start by looking in the Web Front Panel_class\Private\Object Factory.vi. This VI is what identifies each object and figures out the type that it is. The Init state looks at the control ClassName, then goes to other states based on that. You can probably just duplicate the String class and do what it does (which isn't much) until it goes to the Finish state. Here we create the new object class. Here I think you can go into the Select object class type. Now how do we update the object we just made? Open the Front Panel Objects\Select_class\Get JSON Data.vi and edit it to support the combo box class type. This VI at the moment assumes the data is always a numeric, so you'll need to do some type checking, or maybe attempt both the variant to data on string and numeric and use the one that doesn't generate an error. Or feel really adventurous and update the Front Panel Objects\Select_class\Attributes.ctl to have the added attribute of Numeric, or String which can be set in the Object Factory. If you do add this to the cluster, be sure and update the value to numeric when a ring, or enum are used. Then the last thing is to look into what to do when the user changes a combo box control value. Update the Front Panel Objects\Select_class\Set JSON Data.vi and set the combo box with new control values. It will return a numeric of which item is selected, so you'll need to look up the list of available items from the combo box and set it. Again if you update the Attribute type def you'll know to treat it as a string or numeric. Otherwise you can look at the data type of the control, or the class the control belongs to. But since this will be called a bunch of times the more efficient method might be to update that type def to contain things like what the data type or ClassName is. This will have a limitation that a combo box can't have a value that is undefined or not in the table. Not sure what would be needed to support that but it would probably involve looking into the web control support. If you give more information on the other two controls that aren't being updated I can try to help. Are the controls just normal string? If they are images do they update? I realize you can't control them then, I'm just trying to figure out what it could be

https://m.youtube.com/watch?v=v6X4QkYQTZU&feature=youtu.be

Hello besides I can hardly discuss on a deeper developer level like it was in the middle of this discussion, I'd like to give some feedback to the initial question: Yes, me. No, seriously: In my opinion, netCDF4 has - despite "only" being some kind of fork on top of HDF5 - some conceptually important differences, which are for me personally the reason to choose it again and again before HDF5. (I looked some times towards HDF5 because of the existing LV-interface, but I always found it to be too general for my needs.) The data I receive from my measurement device is n-dimensional, while n can differ from measurement to measurement. This was the main reason I was searching for something different than tdms or just ASCII-files. Important for my point of view is that the independent variables of such a dataset are coordinates and I want that information to be stored in the data file. Perhaps this is best described here http://www.unidata.ucar.edu/blogs/developer/entry/dimensions_scales. So what I did was running the LV-assistant for creating wrapper-VIs for given c-headers and the adjusting manually step by step the things to be made that it runs without errors... But I have to admit that this usage of netCDF4 has not made it into my main every days LV-project which runs my measurement device for years now. It's still part of the new beta-like project - but it works and produces fine nc-files.

Hi guys; As a friendly heads up, the LabVIEW compiler for RasPi has been released (can you hear my sigh of relief through my post?)... The downloads and documentation are available on this Github repo. Cheers and hope to see you all at NIWeek 2017. I'm supper excited with the possibility of no longer being on the verge of a heat stroke in Austin every NIWeek... This coming one will be my NIWeek number 17 and it will be a new experience for sure. If I don't catch you at the LAVA BBQ, come to our booth to say What's Up.