Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/07/2011 in all areas

  1. Awesome! I've just printed this and placed it on my cubicle wall next to my 'How to be an expert' chart (see below)
    3 points
  2. Today's cartoon, for those of you that don't have XKCD in your RSS feed.
    2 points
  3. Too slow/too much effort to file a bug. The situation I was realizing I need this feature is when you are in 'the flow'. You go through implementing a new feature and you touch/change a SubVI in another 'code modules' to make your new implementation working. In this situation making the SubVI 'clean' would throw me out of 'the flow'. I want just a amazon-one-click-buy-button to mark that SubVI as dirty and go back there later, when the 'big-picture' is implemented. But it would not be a bad idea to have an option to sync these statuses with a bug tracker like mantis (e.g. by writing the status in a data-base), as well as to have any status changes in the Changelog of my SCC (maybe as pre-commit hook). Felix
    1 point
  4. One option is to use a Issue tracker (or bug tracker), like Mantis. NI offers the Gateway tool for this, but i don't know if it can track to the VI-level about a state of the VI. Ton
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.