crelf

QUOTE (Attila @ Sep 19 2008, 07:21 AM) That's not enough info to diagnose the issue - please post your code.

QUOTE (jpdrolet @ Sep 18 2008, 07:50 PM) My work here is done

QUOTE (dannyt @ Sep 15 2008, 07:23 AM) OK, I can't be mean anymore - the link doesn't actually reveal the final Cylon - it's a link to an actual bread-toasting toaster that the people at BSG thought would be a good marketing product Trust me: you can check it out without fear of finding out who the final Cylon is*. * ...or can you? :ninja: Does anyone else like The http://www.cbs.com/latenight/latelate/' rel='nofollow' target="_blank">Late Late Show with Craig Ferguson as much as I do?

QUOTE (Yair @ Sep 18 2008, 12:39 PM) ...and in menus.

QUOTE (shoneill @ Sep 18 2008, 01:55 PM) That's what keeps me coming back...

QUOTE (jcarmody @ Sep 18 2008, 12:43 PM) I don't mind scrolling, as long as it's limited to scrolling in one direction only. LabVIEW is (by both nature and nurture), a left-to-right language, so hooking up error clusters and other dataflow-forcing elements, diagrams are usually wider than they are tall, so I often write VI's that scroll horizontally, but very rarely vertically. QUOTE (jcarmody @ Sep 18 2008, 12:43 PM) I mentioned that students in a few LabVIEW Basics classes had asked me about a zoom feature. His answer was that NI has resisted doing that so as not to encourage large block diagrams. I wonder why they even have the navigation window. Because people want(ed) it Before the navigation window, there was Bird's Eye View (the older version available through OpenG). There must have been a need, otherwise they never would have been developed...

QUOTE (JustinThomas @ Sep 18 2008, 10:31 AM) That's a good point. From the help: "force destroy? If FALSE (default) and you want to destroy the queue, either call the Release Queue function a number of times equal to the number of times you obtained a reference to the queue or stop all VIs using the queue reference. If TRUE, the function destroys the queue and you do not have to call the function multiple times or stop all VIs using the queue reference." In that case, I don't think that the extra code does anything...

QUOTE (FLAnatic @ Sep 18 2008, 10:03 AM) Thinking out loud: The first VI either creates a new queue, or obtians an existing queue (if a queue of that name and datatype exists in memory) - I wonder if they're trying to make sure that if the queue already exists, it's destroyed, then recreated.

Just a quick reminder: the broad policy of the LAVA Lounge is "Enter the lounge and discuss anything and everything. Nothing is off-topic and all discussions are encouraged." If you don't like what's posted, then stop reading the thread.

QUOTE (yazdihr @ Sep 18 2008, 09:22 AM) You shouldn't need the NI card - it should work fine on any ethernet card. QUOTE (yazdihr @ Sep 18 2008, 09:22 AM) Using TCP/IP sounds a cheap and easy way to start with. Right - you *could* work at the TCP level, but why spend the weeks it would take to write a driver when you can just buy one that has more features than you'll ever need? QUOTE (yazdihr @ Sep 18 2008, 09:22 AM) ...in the past I have used Data Socket and I think it was very slow! Very very slow... I sure can't argue with that - it's not really what datasocket was designed for - it was just a little hack I found. You'll never get anywhere near streaming rates using it - it's only good for relatively static images (update every few seconds).

QUOTE (iowa @ Sep 10 2008, 12:51 AM) Here's a quick example that I just threw together:

QUOTE (CRBreingan @ Sep 17 2008, 11:40 PM) Here's an example that I threw together very quickly - it shows a live webcam from LAVA headquarters...

QUOTE (sam @ Aug 4 2004, 03:22 PM) That's pretty cool It's simple, and it works.

QUOTE (CRBreingan @ Sep 17 2008, 02:28 PM) Our admin's working on fixing that. Stay tuned QUOTE (CRBreingan @ Sep 17 2008, 02:28 PM) ...dose it only connect with GigE and IEEE 1394? Is there any way that i can get this ethernet camera to appear in MAX? Yep - that's one thing that it does, amongst plenty of other things. It's basically a link between your camera and LabVIEW (with MAX included). It works with IEEE 1394, GigE, as weel as all the NI IMAQ cards (progressive scan, interlaced, CameraLink, and plenty more). QUOTE (CRBreingan @ Sep 17 2008, 02:28 PM) But the datascoket that you linked has been "moved or deleted." What's the format of the image (eg: bmp, jpg, etc), and what version of LabVIEW are you using? I should be able to throw something together quickly for you to use in the interim...

QUOTE (TobyD @ Sep 17 2008, 02:09 PM) heh heh heh

QUOTE (TobyD @ Sep 17 2008, 12:09 PM) Now you're getting it!

QUOTE (CRBreingan @ Sep 17 2008, 11:40 AM) If you know where the image is, you should be able to use this: http://forums.lavag.org/Downloading-an-image-from-a-Web-server-using-Datascoket-t100.html' target="_blank">Downloading an image from a Web server using Datascoket

QUOTE (neB @ Sep 16 2008, 06:55 AM) Ahhhh - but it doesn't look wrong to the trained eye The structure has that cute striped background which shows that not only is that code never run, but it's actively stripped from the code at compile time. More info: Fuzzy Wires and Constant Folding in LabVIEW. QUOTE (Ton @ Sep 17 2008, 12:35 AM) LabVIEW with http://en.wikipedia.org/wiki/Late_binding' rel='nofollow' target="_blank">late binding .

QUOTE (CRBreingan @ Sep 16 2008, 06:30 PM) Is the camera compatible with http://sine.ni.com/nips/cds/view/p/lang/en/nid/12892' target="_blank">NI Vision Acquisition? If so, I suggest you use it - it'll make you life a whole lot easier than screwing around with low-level activeX calls, and is feature rich.

QUOTE (Antoine Châlons @ Sep 17 2008, 09:59 AM) We've upgraded a big project from 8.5 to 8.6, and (other than a little niggling namespace issue) all went smoothly...

From NimbleThink: "This VI utilized the VI Strings Levenshtein Distance to compare a test string against an array of strings to find the string in the array which is "closest" to the test string, returning the closest string and the distance."

QUOTE (hfettig @ Sep 15 2008, 02:38 PM) That's not what I'm saying at all - I'm saying that it's a problem between the two, not necessarily due to one or the other.

QUOTE (TobyD @ Sep 15 2008, 11:55 AM) Boom tish! Thank you, thank you, I'll be here 'till Thursday - try the fish!

QUOTE (TobyD @ Sep 15 2008, 11:11 AM) Touche!

I'm not sure if it was your intent, but your post kind-of sounds like you think that Skype using port 80 is a bad thing? I'm not sure it is. It's a chicken and egg problem: if you use Skype first then try to use something else that wants that port then it can be seen as a Skype problem...