Quote:
Originally Posted by Greg McKaskle
Personally, I think a description of the code, commonly with an image is a good approach.
|
I take it you mean a text description, explaining what I want to accomplish and how I did it - right?
Quote:
|
Originally Posted by Russ Beavis
That prints all of the frames just fine but isn't really super navigable.
|
My main interest is showing how stuff is configured behind the icon.
For example, I created a VI (see first post above for a link) that takes an analog 0-5v input, limits it and maps it to a curve (actually an interpolated curve based on a table), scales it and displays it. The idea is to show how an analog joystick input can be mapped to eliminate a victor dead zone while increasing responsiveness where it matters, all while ensuring PWM outputs between 0 and 254. (
Yes, I know I can scale it and map it in one block, making the multiplication block redundant, but I wanted to show one step at a time)
I can print out the scaling and mapping block (one attachment), but how can I show the table (second attachment) that lives within it? That is what's important, not the 'outside' view of the block.
This example is a trivial case - I think - and so one image shows the table. But what about when these blocks get a little bit 'advanced' - will I need to paste a half-dozen pictures to get my point across? How about when the code is for the whole robot?
Has anyone tried to open the VI that I posted? Can you see the table?
I think a good answer to this issue will benefit the whole community.
To anyone who uses LabView professionally: How do you share LV Code?
Don