Jump to content

Saverio

Members
  • Posts

    137
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Saverio

  1. Is there any way to change the character set that the type cast vi uses? Ideally this should be independent of OS settings.

    You're misunderstanding what Type Cast does. Type Cast knows nothing about character sets - it simply reinterprets a sequence of bytes as something else. Consequently, it's not used exclusively for strings. For example, an array of 4 U8 values can be reinterpreted as a single U32 value.

    Does anyone know techniques for displaying special characters and regular characters in a string?

    You can programmatically change the font using the Text.SelStart, Text.SelEnd, and Text.FontName properties:

    font change.vi

  2. He didn't need to change thing. Windows 7 has this "Font size" setting, and for small screens (like laptops) it automatically sets it to 125%.

    I don't think I've ever seen this automatically set to 125%, even on Windows 7. At least I've never seen it set to that on any of the laptops we have here at work, whether the OS came preinstalled from the vendor or whether it was a clean install from disk.

  3. Hi Guys,

    I want to know how I can clean a multicolums list control which has been filled of old data. Does anyone know how to do that efficently?

    I have already tried to pass an empty string array to the Item Names property of the control but it doesn't work.

    I don't quite understand why this didn't work. It certainly should work, unless you have a race condition, which would explain why all of the other attempts failed. Try it in a simple VI. If you can't figure out the issue, run the code in highlight execution mode. If it's a race condition, highlight execution mode can usually help to find that error. If you still can't find the problem, then post the VI.

  4. Sorry, I was explicitly referring to the "inclusiveness" in terms of whether it's a bug or not. You seemed to be implying that the non-inclusiveness is a bug. In actuality, the bug is that in the second case, LV 2010 is not behaving correctly. When you wire in a constant it does one thing, but when you wire in an output of a string function it does something else. That seems to be a compiler issue. In LV 2011 it behaves correctly, i.e., according to the documentation. You may disagree with it, but that does not make it a bug. ;)

    I do not know the reason why the string range was made non-inclusive. That's something you'd need to ask NI. You can always lobby to have the behavior changed by posting an idea in the LabVIEW Idea Exchange.

  5. From the LabVIEW Help:

    For numeric ranges, specify a range as 10..20, meaning all numbers from 10 to 20 inclusively. You also can use open-ended ranges. For example, ..100 represents all numbers less than or equal to 100, and 100.. represents all numbers greater than or equal to 100.
    For string ranges, a range of a..c includes all strings beginning with a or b, but not c. A range of a..c,c includes the ending value of c.

    Not a bug.
    • Like 1
  6. There are numerous programs available that you can use to create .chm files. The good ones are, of course, not free. Or, if they are free, they're only free for personal use, not for a commercial product. I actually use Kompozer to create the HTML pages and Microsoft HTML Help Workshop to create the .chm files. Kompozer is a little buggy, but it gets the job done. HTML Help Workshop is not very intuitive, and its user interface is archaic and downright user-unfriendly, but hey, it's free.

  7. Well, the "hackability" is still there - it's just that the specifics detailed in the reply on Stackoverflow didn't seem to apply directly to LabVIEW 2011. But then I'm not an expert in interpreting assembly language.

    Of course, I wonder if NI can sue that poster for providing such details which, to me, seem to be a blatant violation of the license agreement.

  8. There was a follow-up to a 2006 thread made over at the NI forums by the user TorPedoCXC claiming he could crack passwords using his GPU (http://forums.ni.com/t5/LabVIEW/VI-s-password/td-p/310730/highlight/false/page/3). He was basically saying the same thing about the MD5 hash. Maybe it's the same user.

    The second method won't work with 2011 since that hex pattern doesn't exist. I checked. I also looked for the method he described in going and searching around a starting offset. No go. Not too surprising since the original was in reference to LabVIEW 8.6.1.

    Does it trouble me? No, not really. If it can be cracked it will be. The protection is there to prevent those of us who are just "mundanes" to be able to skirt the protection. Anyone who's determined will get around the protection. Of course, the legal repercussions of doing so are another matter.

  9. Not sure if this fits the bill for you, but maybe a MikroTik RouterBoard might work for you. These things are fully programmable, so you can make it do just about anything you want. Don't know if they fit your size requirement, but the most seem to fit your power requirement. I will give you one warning: learning to configure these things is a steep learning curve.

    • Like 1
×
×
  • Create New...

Important Information

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