messing up block diagram code

[Wiebe@CARYA]

What can be very confusing is putting pictures of LabVIEW objects in your diagram. Preferably above other objects.


Also, making completely white or transparent (one pixel needs to be not-transparent) vi's, or vi's with pictures of objects in the icon.


Not sure how to reverse this automatically (or to generate it automatically). It will be a lot of work, and the results will be questionable. Are you trying to confuse a colleague?


Regards,


Wiebe.

[Wiebe@CARYA]

Well, a VI that turns messed up diagrams into cristal clear diagrams would benefit a lot of people!

The other way around is indeed a bit strange.

Regards,

Wiebe.

[tbob]

I'll join the ranks of those who think hiding code rather than using password protection sounds silly.  But who knows, there may be a very good reason for it.  Like developing code for a customer where the customer wants to own the code but the author doesn't want the customer to change it, so he gives the appearance of hidden or jumbled code.  Of course any good labview programmer could unscramble any mess.  Anyway, the attached vi is an example of totally hidden code.  5 stars to the first person to unhide the code.  It is in LV 8.2, sorry I don't have any other version to save it to.

[altenbach]

---

wiebe@CARYA wrote:
Well, a VI that turns messed up diagrams into cristal clear diagrams would benefit a lot of people!

---

Talk about a toolkit that would sell billions! 😄

In the meantime, Maybe Darren could extend the VI analyzer to autocorrect all found flaws. 🙂

[altenbach]

Your code violates the requirements that the code be visble.

To find the code, just use execution highlighting, then remove the obstructions.

Message Edited by altenbach on 08-29-2007 09:20 AM

[AnalogKid2DigitalMan]

The wizard beat me using the same method.

[Wiebe@CARYA]

You would need a way to refere to each object in a unique way. If someone would edit the messed up VI, the ordering of the objects before and after might not be the same.

Why not simply mess up the diagram and keep a copy of the original? Then you can always revert the diagram (or actually there is no need to do that anymore).

Regards,

Wiebe.

[tst]

It's always nice to see everyone trying to come up with tricks to do what is an essentially useless exercise.

My idea was also to create an obfuscated copy and to perform the obfuscation by doing a recursive inlining followed by moving all the code to a single point.

BTW, every object can have tags associated with it (that's a private feature), so the required information could be embedded in those tags, but it's quite a useless exercise.

[Wiebe@CARYA]

Useless, but fun!