Sparkette

QUOTE (Val Brown @ Mar 21 2009, 05:37 PM)

In other words, you're wanting to hack their security and bypass it. I understand curiosity but, from where I sit, that's not just curiosity, it's tresspass.

How would it be trespassing if it's my own computer?

I recently upgraded LabVIEW to 8.6, and I noticed that the Tank indicator has gone missing. It's always been there before, but now it's just an empty space in the controls palette. What's going on?

QUOTE (Val Brown @ Apr 4 2009, 04:15 PM)

Isn't this kind of like your other hacking question? What is motivating you to try so many hacks of LV?

I just believe that software should never have features not revealed to the end users, with the prominent exception of easter eggs. If a file format has a certain feature, the program should allow anyone to use it, not just the developers.

QUOTE (Mark Yedinak @ Apr 3 2009, 04:49 PM)

The difference here is that NI is changing the data type, not you the user. They have knowledge about the type of data and at this point they do not expose that level of customization to the user.

What reason would they have for keeping it private? Can anybody from NI maybe post here and say?

QUOTE (Mark Yedinak @ Apr 3 2009, 04:38 PM)

As far as I know you can't change the appearance of the wire type for anything other than a class.

Well then how did NI do it with the matrix typedef?

If you have ever played around with the matrix data type, you may have noticed that it is actually a 2D array in typedef form. But if you disconnect it from the typedef, the wire appearance ("[][][][][][][][][][][]") goes away and is instead replaced by the standard "===============" wire appearance. It is obvious that the custom wire appearance is stored in the typedef. But my question is how can I change the wire appearance for my own typedefs? I know how to do it for classes, but those are different. Does anybody know how to do it in typedefs?

Is there any way I can acquire the RF signal from my Wi-Fi card and put it in LabVIEW? It should be possible, as all the hardware is right there.

I was fiddling around with Cheat Engine and LabVIEW, and I found that it seems to be counting the number of times I access the context menu on a numeric constant. Does anybody know what's going on? This doesn't seem like something LabVIEW would need to keep track of!

Is there any USB hardware compatible with LabVIEW which can let me get a taste of the hardware interfacing features in LabVIEW that I don't need to shell out hundreds of dollars for? There's got to be something in the sub-$50 price range which can be controlled by LabVIEW over USB. Any ideas?

Here's another one I made. It's basically just like a digital flip-flop. Don't know how useful it would be in a professional environment, but cool nonetheless.

QUOTE (Yair @ Mar 23 2009, 03:18 PM)

The format LabVIEW uses is called PICC. It's undocumented and has no public editing tool.

You can use EMF to partly achieve the effect that you want, but it won't always work as you wish. You can see some example in http://forums.ni.com/ni/board/message?board.id=170&message.id=231915' target="_blank">this thread.

Trial and error, anyone?

Try these steps:

1. Place a Round LED from the Classic category on your front panel.
   
2. Right click it, then select Advanced-->Customize...
   
3. Click the wrench in the toolbar of the new window
   
4. Right click the actual LED (not the label)
   
5. Click Copy to Clipboard
   
6. Close that window and click Don't Save if prompted
   
7. Click Edit-->Paste in your front panel.
   

I know LabVIEW can use metafiles, but this is clearly not a metafile, as the edge of the LED retains its shape when resized. Besides, with it copied, if you paste it into any vector graphics application, it simply pastes as a bitmap. And if you import a metafile, you can't change the color of it in Properties. This is some sort of LabVIEW internal vector format. Anyone have any clue as to how to create these images so you can customize controls better?

This one takes in a number of points, and draws the polygon in an XY graph. It outputs the points in a cluster of X and Y arrays.

PMS? Really...

Oh wait, it's already mentioned. Never mind!

QUOTE (Val Brown @ Mar 21 2009, 03:40 PM)

Why exactly do you want to do this?

Two reasons:

1. I am curious as to how some of the built-in password-protected VIs work (i.e. Picture to Pixmap)
   
2. I may be able to find additional undocumented features.
   

Also, to respond to Yair's comment, maybe someone on the forum could find a method, advertise on the forum that they can do it, but not tell how for fear of NI finding it. They can't "fix" something if they don't know what it is, right?

QUOTE (Aristos Queue @ Mar 21 2009, 01:01 AM)

The token no longer works after LV 7.1.

Does that mean I can't use VI Scripting after 7.1?

Okay, so I enabled scripting using the

SuperPrivateScriptingFeatureVisible=True

line in my INI file, and additional properties were added, but the Block Diagram one wasn't! How do I get it there! I'm using LabVIEW 8.5.

Didn't we first find out about VI scripting through VI's that NI forgot to password-protect? When password-protected VI's are run, the computer surely accesses the block diagram at one point or another, so obviously it is possible to read the block diagram. LabVIEW just won't let us see it. Can anyone find any way to force it to show you? Perhaps by hex-editing the files or even using Cheat Engine or something?