LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Top Kudoed Authors
Showing results for 
Search instead for 
Did you mean: 

Rotate String


                     this time, I hope this idea was not already proposed! Smiley Frustrated





Trusted Enthusiast
Trusted Enthusiast


Active Participant

As a question to X.'s suggestion:

 Is it correct to say that the "string to byte array" and "byte array to string" simply change how we choose to view the data (no data or structure change) and as such there is extremely low (no?) overhead with these functions? I would hope the compiler can do it that way.. (I have wondered this many times, but never could be bother to benchmark or ask before..)

If that is the case (very low/no overhead) then I don't see much point in making that functionality a new palette item, but on the other hand it would be a very easy thing for NI to do..



CLD LabVIEW 7.1 to 2015
Trusted Enthusiast
Trusted Enthusiast

My point in suggesting the obvious was that there is very little code to write to get the desired functionality. Personally, I never had to rotate a string, but I would suspect that this is a pretty rare need.

As far as what the function does, I can only guess, but strictly speaking, in other languages, a string is not JUST a byte array (see for instance this discussion). However, to confuse things a bit, if you look at the allocated buffers in the code below:




there does not seem to be any buffer allocated specifically for the string to U8 operation; you get the same buffer allocation in this situations:




and there is certainly none in the reverse operation:




This being said, even if there was data copy, these are only strings... so unless you want to rotate the Encyclopedia Britannica (and even then!), I really wouldn't worry about overhead issues...