Jump to content

Q^Q

NI
  • Posts

    17
  • Joined

  • Last visited

Posts posted by Q^Q

  1. The linked post didn't have an answer.  It looks like it just doesn't support unicode.  But from my recent experience, I can see why it is so difficult to support unicode in LabVIEW.  It is not just showing some characters on the FP or BD.  But the most difficult part is that many many LV projects have non-unicode VI names.  

    This was what I encountered recently:  I had some projects that was using Chinese VI names.  They were built on a Windows that the default language for all non-unicode characters were Chinese.  I couldn't load any of projects either on Linux or on a Windows without Chinese as the default language.   This is because the same bytes of digits represent different characters on unicode and non-unicode systems, and LabVIEW rely on those characters to load a VI.

    I suspect that if LabVIEW starts to support unicode, it will break all the projects that previously built on non-English characters.  

  2. I recently noticed that LabVIEW has different character encoding format for Chinese characters on Linux and Windows.  I'm not sure but feels like that LabVIEW accept and display unicode characters on Linux, but it use non-unicode on Windows.   So, if I put some Chinese characters in a VI on Windows, they cannot be displayed if I open the VI on Linux; if I fix the Chinese characters on Linux, then they will not be displayed on Windows.

    Is there any way force LabVIEW use the same encoding format on both systems?

  3. QUOTE (jdunham @ Apr 12 2008, 01:09 AM)

    Well that's great news. I don't know what it would take to get into a real LabVIEW release, but that would be welcome. If the tool can never graduate from NI Labs in to NI LabVIEW (shipping version), it really isn't much help. Did you find/fix the problem where deletes got into an infinite loop?

    If you wan't some extra homework, it would be extremely useful to be able to independently lock items read from the map so that a save read-modify-write cycle could be performed on a LabVIEW diagram. This can be done with LabIEW semaphores, but then you are adding an O(n) performance hit to get the semaphore.

    Thanks for your efforts Q^Q; it's very encouraging.

    I have some urgent job to do in the two weeks. So, I just made a quick test on the XNode Map code. I think I've found the problems in the Map code. It will be fixed once I finish my current work.

    The XNode Map, unlike the lvclass one, has to manage the memory of all elements data itself. So, its code is much more complicated. (Could have more bugs.)

    NI is investigating the best way of providing common used data structures in LabVIEW. I'm not sure when it will make the final decision. The final app could be the XNode approach or the lvcalss approach, or another approach that includes both advantages of the former two.

    Thanks a lot for benchmarking all of them!

  4. QUOTE (Aristos Queue @ Apr 10 2008, 09:31 PM)

    Thank you for including this one in your test results. I've fielded your posts out to half a dozen NI engineers to evaluate the results and see if there are any obvious slowdowns that can be patched in time for the next release. We'll see what happens.

    I found there are some obvious slowdowns can be fixed easily in it. I tried to change some of its code yesterday, and the performance improve is huge. The result is it runs faster than all the other approaches.

    The original purpose of the LabVIEW Generic Container is just to investigate a way of providing common data structures in LabVIEW. We didn't put much effort on its performance.

    Hopefully, we will release a new version of it with better performance in a couple of months.

  5. Hi, i'm new on this forum but i think i can help on your problem :P

    I think you can use time-out option of Event Structure.

    You can see an example on the picture attached.

    Best regards :)

    Good!

    This structure helps me solve the problem.

    Thank you!

×
×
  • Create New...

Important Information

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