Leaderboard

It's weird behavior for a weird use case but it appears to do what it says it's going to do. https://zone.ni.com/reference/en-XX/help/371361M-01/lvhowto/case_selector_values/

For windows users a nice alternative to XAMPP is using the Windows Internet Information Services to set it I followed the Steps on the link bellow: https://www.techwalla.com/articles/how-to-set-up-a-web-server-in-windows-7

You'll find that OpenG is the most common LabVIEW reuse library there is. It was originally developed around the LabVIEW 4 era (as far as I can tell) and has several major updates and improvements, but hasn't been updated recently. It predates VIPM, tools network, and LabVIEW projects. Since OpenG is so commonly used in the community, many members forget to list it as dependencies (myself included). With the very open BSD license, there is little reason to not just install OpenG with every copy of LabVIEW. Look around your newly added palette and you'll find all kinds of awesome useful tools. The Array palette is probably the one I use the most, but File I/O, LabVIEW Data, Application Control, and Variant Config are also very useful.

well hes probably made a generic tcp function which takes his local cluster and transmits it like an RPC style thing. If you're saying the german char is in the variant I'd suggest adjusting the code on the sending side to use this: http://digital.ni.com/public.nsf/allkb/45E2D7BE36CE3E8B86257CCF0074D89B keep in mind the type is a variant, so you have to be careful about how the receiver gets it. Note the code in the KB -- if you use this function to flatten an entire cluster, then the receiver doesn't get a string representing the flattened cluster, it gets a string representing a flattened variant, which represents the cluster. So if you were to use this I'd suggest using it *just* on the variant part of the data. The complexity of doing so depends on what else is in the cluster and how labview stores data in memory ( http://zone.ni.com/reference/en-XX/help/371361N-01/lvconcepts/how_labview_stores_data_in_memory). If the german char is in the string, well the flattened representation of a string has probably never changed -- its 4 bytes for len followed by the data. So in this case I'd guess its more likely to be an issue with how the ue or oe are represented in whatever character set is in use....but this is about the extent of my understanding of character sets in labview. I'd suggest doing what inf{} said above, maybe trying to reproduce a very simple case, or potentially using the unicode tools ( https://decibel.ni.com/content/docs/DOC-10153) to convert characters from window->utf8 and back again.

Yup, the .Net part accepts many different image types. ICO is one of them so I pass in the stream that is an ICO file that is then displayed in the PictureBox, or saved back as a new PNG stream. Same with all the other file types, .Net opens a JPG and displays it, then saves it as a PNG stream, then LabVIEW interprets it as LabVIEW data.