Conducting a peer review

[LV_Pro · Accepted solution]

I have been dropping free labels beginning with my initials a space - space, description anywhere that there is a question about the code, in mine or others (i.e. "pwm - this for loop shouldn't autoindex"). I've begun also adding an arrow (from the block diagram's "structures/decorations") to point exactly where I'm talking about, incase there is any question. A simple text search will find them. To make them more generic, when working with a team, I have gotten everyone to proceed the initials with something like ***   (i.e. "*** pwm - this for loop should autoindex"), so that the text search will find multiple commentors additions. Use a contrasting color, different than the normal comments (which also should be in there).

 Asked my "boss" for a bigger monitor that the square 19" LCD, just got a wide screen 24". Wow, I'll be able to put much more on a diagram now!      It does allow me to have more vi's open and visible though.

[RS_233]

I think that's what I'll end up doing.  Putting in "*** [initials] - [comment]" is the best possible solution that I can see at the moment (although having the cursor X and Y would be better still).

The code capture tool looks interesting.  However, I don't think it would be too useful.  Having a specific location in a given diagram is still the standard, imo.  If there is a particularly large block diagram (not everyone writes nice and compact ones 🙂 ), having a small subset of it doesn't give me the best information where the specific code is located.

Thanks for the info guys.

[kkroninger]

Thank you for explaining where the arrow decorations are. I could not find them before. What are they doing hiding with the while loops? lol.

[JÞB]

I've been known to drop this vi on my BD next to comments (I can go and search the heirarchy for all instances of it ) and it helps me never forget to go back and do something I thought about- 

[SteveChandler]

Jeff, that sounds like a pretty good idea. I have just used text labels for that. I updated your vi slightly to make it look way cool on the block diagram.

[JÞB]

Thanks Steve,

As a bonus- guess where I have the vi saved and why it is there?

Spoiler

In vi.llb of course!   so I can ignore it in the heirarchy view

[SteveChandler]

Answering without reading the spoiler. vi.lib so that it is not part of a project and is available to all projects?

Edit: Doh! I got half of the answer.