topic Re: Labview logo in BreakPoint

Labview logo

nogoodreason — Fri, 22 Jan 2016 22:28:00 GMT

I think that Labview needs to change their logo, because it shows a picture of a red line and a blue line going in to an addition block. Everybody knows that when you add red and blue you get purple. come on guys.

Re: Labview logo

PeterFoerster — Mon, 25 Jan 2016 07:17:31 GMT

I think they should first get rid of the Sequence Structure in the logo, which they already partially did. If we view the red as orange, it is correct: DBL + Int = DBL.

Re: Labview logo

Hooovahh — Mon, 25 Jan 2016 13:47:28 GMT

What no coercion dot? What is this LabVIEW 2?

(I honestly don't know if coercion dots were in LabVIEW 2)

Re: Labview logo

PaulG. — Mon, 25 Jan 2016 14:18:48 GMT

I helped a new department get started and we needed a logo.

The company was too cheap to hire an ad agency so we had a contest.

Re: Labview logo

PeterFoerster — Mon, 25 Jan 2016 15:32:25 GMT

That's brilliant... Works every time.

Although after watching Mad Men I'm not sure I would give them my money, either.

Re: Labview logo

AristosQueue (NI) — Mon, 25 Jan 2016 16:28:31 GMT

@Hooovahh wrote:

What no coercion dot? What is this LabVIEW 2?

Who says that's an Add primitive? That's just a VI that uses the same icon. And those wires going in? There's no coercion because those are two LabVIEW classes whose wire appearance has been customized. And that supposed "sequence structure"? That's just a pasted image sitting behind the code. You can tell because there are no tunnels.

🙂

Re: Labview logo

Jacobson-ni — Tue, 26 Jan 2016 01:13:08 GMT

@AristosQueue (NI) wrote:

@Hooovahh wrote:

What no coercion dot? What is this LabVIEW 2?

Who says that's an Add primitive? That's just a VI that uses the same icon. And those wires going in? There's no coercion because those are two LabVIEW classes whose wire appearance has been customized. And that supposed "sequence structure"? That's just a pasted image sitting behind the code. You can tell because there are no tunnels.

🙂

I don't know what you're all talking about. Clearly it's just two channel wires being added together.

Re: Labview logo

AristosQueue (NI) — Tue, 26 Jan 2016 16:26:20 GMT

Jacobson wrote:
I don't know what you're all talking about. Clearly it's just two channel wires being added together.

Well, that's the 2016 patch. The great secret is that we've actually updated the logo every release of LabVIEW, but in a way that is completely transparent to our users. It was only an Add primitive in LV 1.0. It was a reentrant VI by 2.0. 🙂

Re: Labview logo

Yamaeda — Tue, 05 Apr 2016 06:36:57 GMT

@AristosQueue (NI) wrote:
@Jacobson-ni wrote:
I don't know what you're all talking about. Clearly it's just two channel wires being added together.
Well, that's the 2016 patch. The great secret is that we've actually updated the logo every release of LabVIEW, but in a way that is completely transparent to our users. It was only an Add primitive in LV 1.0. It was a reentrant VI by 2.0. 🙂

I take it it's now set to Run when opened?

Re: Labview logo

Sam_Sharp — Tue, 05 Apr 2016 07:53:45 GMT

I'd also like to think that any PNGs of the logo are actually VI snippets...if you drag them onto the block diagram they release the *true* power of LabVIEW.

Re: Labview logo

Hooovahh — Tue, 05 Apr 2016 12:43:24 GMT

How awesome of an easter egg would that have been? (or is?) that some random PNG file installed with LabVIEW is actually a VI...

Re: Labview logo

Hornless.Rhino — Wed, 06 Apr 2016 02:22:06 GMT

@Hooovahh wrote:
How awesome of an easter egg would that have been? (or is?) that some random PNG file installed with LabVIEW is actually a VI...

Just think, the millions of PNGs sitting on servers all over the world, and any one of them could potentially be a VI.

Re: Labview logo

Sam_Sharp — Wed, 06 Apr 2016 09:03:35 GMT

Then they all activate at once and the LabVIEW version of SKYNET arrives!

/removes tinfoil hat

Re: Labview logo

PeterFoerster — Wed, 06 Apr 2016 10:30:42 GMT

@Sam_Sharp wrote:
Then they all activate at once and the LabVIEW version of SKYNET arrives!

/removes tinfoil hat

Since LabVIEW is running <sarcastic quotation marks> really stable <\sarcastic quotation marks> today, I'm not that afraid...

Re: Labview logo

Ben — Wed, 06 Apr 2016 15:10:50 GMT

@Hornless.Rhino wrote:
@Hooovahh wrote:
How awesome of an easter egg would that have been? (or is?) that some random PNG file installed with LabVIEW is actually a VI...
Just think, the millions of PNGs sitting on servers all over the world, and any one of them could potentially be a VI.

The paranoid side of me read that as...

"Just think, the millions of PNGs sitting on servers all over the world, and any one of them could potentially be a VI.rus"

Ben

Re: Labview logo

JW-JnJ — Mon, 11 Apr 2016 13:02:05 GMT

@Sam_Sharp wrote:
I'd also like to think that any PNGs of the logo are actually VI snippets...if you drag them onto the block diagram they release the *true* power of LabVIEW.

So, you mean like this?

(wasn't sure if it would carry over if I inserted as image)

Re: Labview logo

Sam_Sharp — Tue, 12 Apr 2016 09:30:17 GMT

Very clever. I'm curious - how did you get the snippet without the normal snippet headers - using the Lava code capture tool, or something else?

Re: Labview logo

JW-JnJ — Tue, 12 Apr 2016 12:06:22 GMT

@Sam_Sharp wrote:
Very clever. I'm curious - how did you get the snippet without the normal snippet headers - using the Lava code capture tool, or something else?

From what I understand (not entirely sure), the code is stored in a metadata section of the PNG file. The visual part of the image is just decoration.

LabVIEW's snippet tool, edit with MS Paint, Paste new image, Save

Re: Labview logo

crossrulz — Tue, 12 Apr 2016 12:14:50 GMT

@JW-JnJ wrote:
LabVIEW's snippet tool, edit with MS Paint, Paste new image, Save

So simple. I can't believe I haven't tried that. Oh, the chaos that will ensue!

Re: Labview logo

Hooovahh — Tue, 12 Apr 2016 12:31:33 GMT

Yeah I don't remember where I saw it, but I remember finding a VI (or maybe it was freeware) that would take a PNG and show you the chunks that were in it. Chunks are just named, with byte offset and length and contain anything you want usually used for meta data. One chunk may contain the actual image. For a VI NI just make one whole chunk the VI file. So if working in MSPaint does work it is probably because the PNG file just replaces the chunk associated with the image data, but leaves all the other chunks that already exist. I suspect the CCT source would tell you more about how chunks are written.