mje Posted September 20, 2012 Report Share Posted September 20, 2012 I speckle my code with tons of TODO comments when I develop. When I find time, I'll often do a search for "TODO" and see if I can hammer any of them out, but in LabVIEW all I get is the name of the VI of any comments the search finds containing my search text with no context as to what any of the items are (unlike say the exceptionally useful task list in Visual Studio). Has anyone written a tool that allows me to scrape stuff like this from my project VIs? I'm aware of the various idea exchange entries, I'm just wondering if there's anything out there that will do the job now. 1 Quote Link to comment
Popular Post JamesMc86 Posted September 20, 2012 Popular Post Report Share Posted September 20, 2012 (edited) Check out https://decibel.ni.c...docs/DOC-15560. It's quite a nice little utility built on scripting. It will pull anything with a colon in the first 10 characters in the diagrams. Edited September 21, 2012 by asbo Fixed your link 3 Quote Link to comment
todd Posted September 20, 2012 Report Share Posted September 20, 2012 The period snuck in: https://decibel.ni.com/content/docs/DOC-15560 Quote Link to comment
mje Posted September 20, 2012 Author Report Share Posted September 20, 2012 Brilliant! If only I could "like" that post more than once, that's exactly what I was looking for. /cheers Quote Link to comment
Yair Posted September 23, 2012 Report Share Posted September 23, 2012 Another alternative is simply to create an empty TODO VI (a red or bright green icon for it is a good idea) and simply drop it there. Then, you can do a find all instances on it and go through the instances. 1 Quote Link to comment
JackDunaway Posted September 25, 2012 Report Share Posted September 25, 2012 Another alternative is simply to create an empty TODO VI (a red or bright green icon for it is a good idea) and simply drop it there. Then, you can do a find all instances on it and go through the instances. Go a step farther, and make the VI broken. One easy way is to make one input "Required" -- then you can "turn off" the compiler error by creating a constant on that input. This forces yourself to go back and fix it, ensuring you can't forget and, say, make a build without the fix. Quote Link to comment
Phillip Brooks Posted September 26, 2012 Report Share Posted September 26, 2012 Go a step farther, and make the VI broken. One easy way is to make one input "Required" -- then you can "turn off" the compiler error by creating a constant on that input. This forces yourself to go back and fix it, ensuring you can't forget and, say, make a build without the fix. Or maybe a required output? Don't know if this is still possible... Quote Link to comment
mje Posted September 26, 2012 Author Report Share Posted September 26, 2012 Most of my to do items aren't things that strictly need to be done so I wouldn't want to break code with them. They're usually along the lines of notes to work on inplaceness, or reminders of the limitations of some placeholder code which eventually need to be ironed out. I do like the idea of a subVI though! Quote Link to comment
hooovahh Posted September 26, 2012 Report Share Posted September 26, 2012 Most of my to do items aren't things that strictly need to be done so I wouldn't want to break code with them. They're usually along the lines of notes to work on inplaceness, or reminders of the limitations of some placeholder code which eventually need to be ironed out. I do like the idea of a subVI though! I'm in this same boat as well. I may want to bring my attention to something later, but I want the code to still be able to be ran. Using something like TODO: and searching for that string (or using the tool posted earlier) helps me see that something is important about the code, without having to break the VI. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.