Benchtop Measurement and Test
Distributed Measurement and Control
Systems Engineering Software
Perspectives showcases how NI sees what’s next in the world of test and technology.
You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.
Provides support for NI data acquisition and signal conditioning devices.
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments.
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.
I would like to be able to
So I propose to extend the search functions with
affected search functions:
Current work arounds:
This work arounds are not as effective as it could be done in core LabVIEW.
For Last Occurence, what's wrong with just putting Reverse String in before you execute the search?
And for Max Offset, is there any reason why you can't use String Subset and then do the search on the subset?
Neither of those two options take up a whole lot of screen space, so I don't see the advantage of your Idea.
I still do see advantages:
This work arounds are not as effective as it could be done in core LabVIEW. When implemented as a function it will be quicker and more memory effective. And when NI realizes it as SubVIs they can probably write more optimized code than me.
Not sure if reverse string is optimized by the LabVIEW compiler. Getting a copy of a big string is a disadvantage.
Doing a String Subset and searching on it could produce a copy of the string in the memory. And shoud the offset input of the search VIs be removed? This could also be done with a String Subset.
And the code for finding the last occurence looks a bit complicated and is not tiny little:
Ah, you're also looking for the index of the last match, I didn't realise that bit.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What do you need our team of experts to assist you with?
We'll be in touch soon!