crelf

QUOTE (TobyD @ Sep 9 2008, 11:58 AM) I'm not worried. I think that it has the potential to be relied upon by LabVIEW users (those who do a little programming, but programming isn't their main job function), but I don't see a lot of LabVIEW developers using it on thier own code (those who program in LabVIEW as their main job function). That said, I can see LabVIEW developers use it on code given to them by LabVIEW users

QUOTE (yazdihr @ Sep 9 2008, 10:52 AM) Sorry - I've got a 1411 you can borrow, but it's PXI.

Our policy on spam is clear: "Spamming is not permitted; please keep all your posts as constructive and on-topic as possible", but we also want to be clear on how our members should handle what they suspect as spam in our forums. From our Golden Forum Rules page: "If a topic is recognized as being posted in the wrong forum, or if the post is a violation of our guidelines then please contact a moderator [using] the report post to moderator feature; please do not respond publicly to the member - a member of staff will do what is required upon contact. Any person/s who attempt to present themselves as a Moderator by posting negatively to a member's topic... will be sent a PM warning and placed into moderation queue upon further actions." In summary, do not reply to a topic that you think is spam - simply click the "! REPORT" link next to the suspect spam (see below) and fill out a description to report it to a moderator. If you do reply to the suspected spam post and don't click on the report button, then the moderators might miss it. Also, you're violating our rules by presenting yourself as a moderator. Foloowing the guidleines will help us keep our forums uncluttered and on topic :thumbup:

QUOTE (Eugen Graf @ Sep 9 2008, 05:20 AM) QUOTE (Kevin Payne @ Sep 9 2008, 04:59 AM) I think you're going to find it difficult to compile a definitive list because there are different educational structures, even within the same country. I agree with Kevin - if you're looking for a general catch-all for everyone, you're not going ot find it (which is why you should include the year of education, so others can have an idea of where they are in teh scheme). The model that you've found is (I think) the US system, and I'm not sure if it applies anywhere else.

QUOTE (BobHamburger @ Sep 9 2008, 12:23 AM) Wrapping subVI code in error cases is an important step toward ensuring smooth integration, along with IEEE Std 830-1993 compliant requirements, detailed up-front design and unit testing (FMEA-driven or otherwise).

QUOTE (yazdihr @ Sep 8 2008, 11:55 AM) PCI or PXI?

QUOTE (normandinf @ Sep 8 2008, 11:19 AM) Nope - I said "...the top ten countries by number of medals..." - Jamaica was 13th by number of gold and 20th by total number of medals.

QUOTE (crelf @ Sep 7 2008, 04:00 PM) Oh - and this is accessible through the Help menu too... QUOTE (Jeffrey Habets @ Sep 6 2008, 05:46 AM) That looks like you really tore it out of a LabVIEW manual

QUOTE (Aristos Queue @ Sep 6 2008, 12:53 PM) I'd love to be on the beta for that. QUOTE (Aristos Queue @ Sep 6 2008, 12:53 PM) ...should such a bugfix release be deemed necessary... QUOTE (Jeffrey Habets @ Sep 6 2008, 05:46 AM) I do agree that it would be a big help if possible generated error's would be mentioned with the VI/function help instead of a seperate place. Everyone probably knows this, but you can right-click on an error cluster and choose "explain error". This pops-up a dialog where it'll give you some more info. As an aside, you can then increment/decrement/change the error code in that dialog to see explinations of other error codes. This also works with http://wiki.lavag.org/Error_handling#Custom_Error_Codes' rel='nofollow' target="_blank">custom error codes too

QUOTE (z3r0 c0o1 @ Sep 7 2008, 12:49 PM) No worries - anytime. If you get a chance, can you please add a link to the jpg string VI? I'd like to tage it so I can find it more easily...

OK - here's the issue: Most folks will tell you that LabVIEW is dataflow - the data figuratively flows along the wires, so when you branch a wire, the value gets branched, etc - this model is often affectionately referred to as "by-value' (or "by-val" for short). IMAQ is one of the very few LabVIEW paradigms that isn't by-value: it's by-reference ("by-ref"). The purple IMAQ datatype is actually a reference to the image that's somewhere in memory, so when you pass that value between VIs, the image data isn't actually passed, but a reference to where the data is. That's why it works with localhost, but not across different PCs: when you're local host, the reference that the sender sends refers to the same memory space as the receiver receives whereas when you're on different PCs the receiver doesn't have the image data in memory, so the reference is to nothing. The reason you're seeing packets passed is that you're sending the reference across UDP - and that takes space. So, now that we've gotten that out of the way, you probably want ideas on how to make this work I suggest that you need to get the image data out of memory and stream that across the network. You're going to need to convert the data to a string, and depending on the resolution and colour depth of your image, that could be a lot o' data and could take some time to get across the network. There's a VI floating around somewhere that convert the data to a jpg string with compression directly from an IMAQ reference - have a dig around on the net... If you get stuck, post again - I'm a little flat-out at the moment, otherwise I'd try to dig up a solution for you...

QUOTE (Irene_he @ Sep 6 2008, 01:56 PM) ...and if you take the top ten countries by number of medals, prorata them by capita, Australia is #1 ! ! ! Okay, that's probably taking it a little too far

QUOTE (z3r0 c0o1 @ Sep 6 2008, 05:47 PM) Welcome! QUOTE (z3r0 c0o1 @ Sep 6 2008, 05:47 PM) After this I tried to broadcast the image over lan and again the same thing, on the localhost there is an image and on the remote pc there is no image, but the number of bytes received is going up. Can you post your code? That would help us a lot in tracking down the issue.

QUOTE (Tredlyn @ Sep 5 2008, 05:22 PM) Feed the path into "Open URL in Default Browser.vi" http://lavag.org/old_files/monthly_09_2008/post-181-1220678630.png' target="_blank">

QUOTE (crelf @ Aug 6 2008, 12:44 AM) For those interested, the financials from the LAVA/OpenG NI-Week 2008 BBQ are in - we made a profit of $145.51. As I've said before, we don't hold the barbie for profit - it's more about getting everyone together. That said, the extra few dollars is certainly appreciated to keep LAVA going As y'all know, LAVA's funded entirely by it's Premium Members, donations, corporate memberships and a little from click-through ads, so every $ helps...

QUOTE (alfa @ Sep 4 2008, 03:05 AM) The IQ test has everything to do with intelligence, http://en.wikipedia.org/wiki/Iq' rel='nofollow' target="_blank">by definition.

QUOTE (Michael_Aivaliotis @ Sep 3 2008, 02:49 PM) Ditto for Oz.

Brilliant!

QUOTE (boyaza @ Sep 3 2008, 12:03 AM) Was there a restart in there anywhere? When do you get the error? Can you post your code?

QUOTE (neB @ Sep 3 2008, 08:06 AM) I'm not sure that alfa would agree that IQ and his calculations aren't exclusive. (how's that for a double negative!)

QUOTE (Justin Goeres @ Sep 3 2008, 07:23 AM) I agree that The Internet has become something that should be personified

QUOTE (Yair @ Sep 2 2008, 12:07 PM) Wow.

QUOTE (Yair @ Aug 31 2008, 02:27 PM) :!: Thread Hijack Warning: I don't use LLBs at all anymore - there's no real use for them IMHO (I'd be happy to discuss, but if you want to hear more, start a new thred and I'll respond there). Better option: zip your files.

QUOTE (Michael_Aivaliotis @ Sep 1 2008, 03:16 AM) I like that the project space doesn't have to mimmick the disk space. Most of us (pre-project) specifically design a disk-based layout that's intuitavely traversable by humans, but that doesn't necessarily mean that programming objects are logically arranged. The project gives me a layer of abstraction from the disk space, so I can arrange things however I like. I think this is one of the least-talked-about features of the project environment, but I love it. I also suggest that this is where the overall computing world is going...