Jump to content

m3nth

Members
  • Posts

    219
  • Joined

  • Last visited

    Never

Everything posted by m3nth

  1. m3nth

    Flash Problems

    Well for general knowledge:
  2. Has anybody seen the latest security vulnerability with Flash? Anybody upgraded and got it to work? I upgraded my PC (I think on accident) and everything that uses Flash quit working (like all the games in the Arcade for example). Now I'm stuck with the new version that doesn't work unless I find the .dll for the old version that has a security hole. I was wondering if anyone actually got the new version to work... if there was something I wasn't doing right perhaps. I'm using Firefox and I tried it w/ both vRC1 and v1.0.7 to no avail (I thought it might be the Firefox version screwing things up). If anyone successfully gets the new flash version running let me know!
  3. You'll have to determine for yourself what's best for you, but I use the attached VI to get the hard drive serial number. It's not set in stone of course, but it is a unique identifier for a computer (so long as the harddrive doesn't change) and it isn't as easy to change as some other things. Edited to say: Well... I have been having problems with getting the attachment to work. I'm not sure if it's the forum or firefox or both. I went back to 1.0.7 after having RC1 but it still doesn't want to attach things. I'll post it if I can get it to work.
  4. What does that mean? I understand PJM's post you quoted--these questions I don't.
  5. I think this is the best idea yet... perhaps you could add it to the wish list. I think that would fall into the category that NI seems to not do too well at sometimes... something along the lines of creating great idioms and widely implementing and enforcing them. The idiom is there (compare / don't compare aggregates, change logic operation, etc etc), but then it's not widely implemented to the full set of functions available.
  6. I'm guessing that the new behavior of the equals operator was implemented for other (more common I'm guessing) types of comparisons which were having problems (in previous versions) when two references were passed to an equals operator. You can always change the code you have now that's broken to the other comparison code you showed--typecast to an integer and check to see if they're exact. However, previous to the new functional implementation of the equals operator, you could not do the internal check that LabVIEW could perform internally to see if the references point back to the same object. With the new behavior in v8.0, this internal check is extracted to the user via the equals operator, so you don't need a special NI VI to do the same thing (see the NI thread and attached VI). http://forums.ni.com/ni/board/message?boar...hreading&page=1 Since the equals operator can only do one thing or the other, I think the behavior in v8.0 is probably better in the long run for the average user because there is extra functionality available via the equals operator that wasn't there before.
  7. Or rather, since you can't select/use them anyway, it's more of an easy way to highlight the properties/methods of a VI that need to be re-coded each time a new version comes out, when the version deprecates certain things.
  8. Michael, I think what you're seeing is one of probably many instances where code was generated originally and then upgraded later (like was already stated). If you have ever worked under the auspices of a large orginization with a strict version control system implemented (which I'm guessing NI has), it's easy to understand why the code looks like crap: you're barely allowed to do anything to it once it's been functionally verified and checked in. I personally don't think that's any excuse for such poorly designed examples as the one above, but at least it makes sense of how in the world they're allowed to release that kind of stuff.
  9. PJM, Got this error message when trying to open your VI: Get Class Name and ID for a Specific LV Version__ClassHierarchyBuilder.vi - The control expected to be at "C:\Documents and Settings\LV Classes Name & Id Tools\Custom Controls\Class Active Status - Enum -.ctl" was loaded from ... No control found for the typedef so I tried to make the control a typedef and it still didn't like that. I eventually deleted the whole event which builds the class list in order to see the saved file. Ok so now that I can actually see the tree.... Is there anyone who can figure out how to create these items using the New Object function or something similiar? (I think it was called New Object).
  10. A note about my previous comment: I originally thought the scripting property nodes were in red, but some of them aren't, and I'm wondering if the red color is actually an indicator of the deprecated items--the color changes from red to light blue if the deprecated item (shown in the previous screenshot I posted) is removed.
  11. Yeah I noticed them... unfortunately it means re-doing a lot of my code :headbang: Has anyone found a workaround for trying to unflatten a null string into a cluster datatype so the cluster is empty? The unflatten function now yields error 42 (generic error), which I suppose can be ignored, but that may be a bit cumbersome.
  12. Only if it's lucrative enough. And Microsoft, just because they have lots of money, doesn't mean they (like anyone else) wouldn't have lots of catching up to do.
  13. For the paranoid, I'll confirm it's a CVI executable, no virus per the latest version of Symantec. I like it... I think it looks very realistic. As with most things of this nature, it runs great when the pixel count is low.
  14. Good grief. Well it's not too surprising I guess. I like the Civilization analogy. I think perhaps what's unsettling from the end-user's perspective, be it with Microsoft or NI or any other giant corporation turned near-monopoly, is the thought of them winding up locked in at a high price-point with few viable alternatives. And whether it's Microsoft or NI or the next big takeover player (Google?), that's exactly where they want you... out of options except for them, with your arm twisted behind your back until it breaks or you say uncle and pay up. No need to mention the many examples of this type of behavior that Microsoft has put forth, especially the latest row they've participated in over the rejection of their proprietary technology by the state of Massacheusetts. So when it comes to NI, I'd say it's pretty valid if there is a general feeling of disturbance over their acquisitions and growing clout. We have already seen the sometimes heavy-handed tactics used to squash or buyout patent lawsuits, the end result of which has been to limit or completely eliminate competition. If you want out, what viable options do you have? Very few, as the state of Massacheusetts and others in Europe have found. Fortunately for them, there are at least open source alternatives that come close, or at least close enough for them to have a viable/workable alternative. For the growing number of dependents on NI however... it will be interesting to see just how long they will continue to be locked in (in various arenas of available software and hardware of course, not in everything by any means) and how far it will all go, as NI strengthens its grip on the market. Also (sidenote here on LabVIEW), I can't forsee NI indefinitely escaping the grasp of a patent lawsuit on the grounds that graphic programming is now (with readily available computing power) one of the most common-sense ideas there is, even though it wasn't at the time that LabVIEW was invented (at which time they received a patent for it, on the grounds, among other things, that it was extraordinary, and not such a common-sense idea). Still though, even if they lost a lawsuit, or if their patent expires (I have a very unclear understanding of when or how that could actually happen), they have still garnered a huge head-start, a set of very mature products, and a large war chest to keep them going for a long time. Guess we'll just have to wait and see what happens next.
  15. I had the exact same problem. At least I think it was the same problem. I compiled a list of the different things you should check, which it looks like you finally figured out. See my old post here on NI... the list is attached to the post as a document with screenshots of everything you can look into: http://forums.ni.com/ni/board/message?boar...ssage.id=115500 Actually... I'll just let the lazy be lazy and post the document here also 'for convenience' Download File:post-360-1130161952.doc
  16. I found a bunch of language stuff that automatically installed with LabVIEW 8, like run-time engine stuff for French/Korean/Japanese/etc, which I don't really want and am pretty sure I won't need. Granted, most people won't care, it's just more disk space, but sometimes I need my disk space. Does anyone know if I missed a custom option somewhere not to install this stuff?
  17. Actually, only one of the old ones works, but not the one for scripting Scripting property nodes actually show up in red.
  18. Not that I care about how nice or sloppy your code looks, but for future reference, if you need to not expose stuff like that you can always just flatten and unflatten your data.
  19. Does somebody that beta tested know what the new icon on the block diagram icon bar is (and what it does)? I believe it's between the lightbulb and the debug-start arrow... it's in some of the Flash presentations on ni.com.
  20. Don't be such a snob. You're right, I don't have the professional version, and that's a good explanation as to why I don't have that file. You know, I was just thinking today about how expensive LabVIEW is. It is REALLY expensive. And I was thinking, why does NI charge that much for it? And the answer in my opinion is just because they can. Not because it's really that super duper special or extra-functional (although maybe it's headed that direction in version 8), but because huge corporations will shell out the dough for it. And if you don't work for a huge corporation, or an educational institution (do they give out pro copies to educators?), then you're screwed. Which is why many people are still using 7 and won't be able to go to 8. Or why they're using even earlier versions and haven't gone to 7. And what does NI do for them? It screws them over especially bad because none of the new files open and nobody can back-save past one version. I'll get off my soap box now.
  21. Lvdiff requires this file in your project directory: procmphier.llb\CMP compare two VIs.vi Since I don't have that file, I'm guessing it's probably in the SCC toolkit or something like that and a good majority of people probably don't have it.
  22. From NI... In case you're curious, the LabVIEW 8 CD / product box / paperwork is not going to actually ship until November. *sigh* If you have a subscription service (lucky you), you'll be able to download your copy earlier when NI notifies you it's available, likely within about 2 weeks.
  23. If I ever managed to stumble across the ability to change my highlighting color, it probably would have been in a century or two. That's pretty cool :thumbup:
  24. This is an uninformed opinion, but I'm pretty sure that application instances are going to solve a whole lot of problems. They might create a few headaches too, but in the long run, it seems like that's a far better way to go when developing in Windows.
×
×
  • Create New...

Important Information

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