Jump to content

crelf

Members
  • Posts

    5,759
  • Joined

  • Last visited

  • Days Won

    55

Everything posted by crelf

  1. Well done! I wasn't sure anyone would know that one
  2. My brain hurts...
  3. Under the "Help" menu, there's an "Explain Error" item, which reports: Warning -200279 occurred at an unidentified location Possible reason(s): Attempted to read samples that are no longer available. The requested sample was previously available, but has since been overwritten.Increasing the buffer size, reading the data more frequently, or specifying a fixed number of samples to read instead of reading all available samples might correct the problem. Looks like you're sampling faster than you can get the data out of the buffer (ie: "buffer overrun").
  4. Therefore, LabVIEW Project Explorer = StarTrek, and a more mature Project Explorer = Battlestar Galactica... (but even BattleStar Galactica had to start somewhere - look at the awesome improvement from the old 80s series to the new one - crikey!)
  5. Add is when there are two terms, sum is when there are more than two.
  6. Hey - where's the ASCII-art attempt at doing this in LabVIEW?!?
  7. That should be developer controllable as well (maybe a setting so we can hide/gray-out that checkbox) Great list Mike - well done!
  8. Interesting - especially since the primitivie itself is called "Quotient and Remainder". That said, it gooes along with the other models they have - eg: the "Add" primitave has an output of "x+y", so it looks like the output is represented as the formulae that arrived at it (I'd prefer NI didn't change the add primitive output to say "add"). Maybe the Q&R outputs could have their equations and then the word in brackets after it?
  9. Great answer! (We're the same here )
  10. What's the error code? Can you post your code here so we can make suggestions? If not, can you post an example written specifically to post that demonstrates the issue? Sounds like a buffer overrun / underrun, but without the error code I'm just speculating...
  11. Excellent point - a little thing that had been pissing me up the wall since the dynamically morphing case structure was introduced Thanks NI!
  12. Hmmm - I wonder if it's because you actually click on it twice - once to open the colour selector and then again to select the colour...
  13. Say's who?!? It's true - I have a life! (and I do use the RSS feed )
  14. :ninja:
  15. I that one!
  16. There's more information here. I use RSSPopper and it's great! Personally, I think the LAVA RSS feeds are the best thing since sliced bread (and that's sayin' something!)
  17. I don't agree, as that splits the arguement into two separate threads: functionality and stability. You might find that the seats are hard in your opinion, but they're still seats. If you expect BMW not to release any cars until their seats are absolutely bug-free, then you'll never get a car. If you expect BMW not release any cars unless their seats are absolutely perfect for you, then you'll never get a car. That's the whole point of improved products - honing them to try to satisfy the market. Which brings me to a second point - the market is constantly changing. But, as often occurs, I digress NI, or BMW, anyone else for that matter, can't release 100% bug-free products - it's just not possible, and I think expecting them to is unfair. If you're really that upset about the number of bugs in LabVIEW (especially in the areas that are important to you) then be active in the beta programme - it's almost like complaining about the government after you didn't vote (one of my all-time pet hates ) Anyway, I don't mean to be too strong here, but I think LabVIEW 8 has been getting a disproportionate bashing of late. IMHO there are a handful of things that I'm not happy with (there will always be since NI isn't developing LabVIEW directly for me), but with the huge advancements I can work around the issues to enjoy the great benefits of the new features. As an aside: nothing inspires people to offer their opinion than if they don't like something - it'd be nice to hear more from those who are enjoying the new version like I am Or am I it?
  18. I've got an RSS feed into my Outlook, so I see LAVA posts within a few minutes of them, but I noticed that LAVA is uncommonly active on Saturday mornings (US time). Does that mean that people usually look at LAVA on weekends, on their own time, at work during the day, evenings? Check out the Poll above...
  19. I expect exisitng components to be better with a new release, but I can't bexpect new things to be better" there's no such thing as "New and improved" - it's either one or the other I kind-of agree - I figure that NI had a target release date and they had to either rush or limit the functionality to get it out by then (hence LVOOP missing from the 8.0 release). The project explorer is a completely different paradigm for LabVIEW - a fantastic new way of doing things that's been pined for for years. I expected a settling-in period Also, we've got a fairly varied crowd here, and if anyone's going to push these new features to their limits, then it's going to be the LAVA crew. Which brings me to an NI critism: unpaid beta programmes are never as efficient and far-reaching as paid beta programmes. An example: I was on the beta programme, and I've got work to do - I could only dedicate a very small amount of time (my own time) to screwing around with it. We were pretty heavy-on for work at the time (still are ) so all I could really do was ohh and ahh over the new features, and not try to really push it with a quasi-real project. I've been saying this for years: if NI contracted a number of people/companies (why not start with the Select Integrators?) to actually develop a real project in parallel to the normal development, I think a lot more of these issues would be stamped-out. Sure, keep the free beta programme too - it's obviously worthwhile, but if you want a dedicated real-world-style project, then paid is the only way to go (let's face it, did anyone on the beta programme do a real project to be delivered to their customer in the beta? I doubt it...
  20. I don't know why everyone's complaining - any significantly large software project is going to have a bunch of irregularities in it - you just need to assess whether the bugs are a true show-stopper for you. It's a trade-off - functionality Vs bugs, and anyone saying they're not interested in the new functionality of 8 and 8.20 is either not a programmer or obviously hasn't used it. Personally, I 8 (and subsequently 8.20) - it's a great development platform with some paradigms that I drool over. Sure, there are a few issues that I have to deal with, but it's been like that since the first software was ever created (if you're waiting for a perfect LabVIEW release, or any other software release for that matter, then you'll die waiting). The only difference between the issues in 7 and 8 is that you've learned to live with the ones in 7 - if you were truly concerned about bugs in software, then you'd never turn your computer on
  21. Sounds like a rant to me
  22. You're welcome - anytime
×
×
  • Create New...

Important Information

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