Leaderboard

Early in this thread, someone posted some VIs for counting the number of lines in a VI. I'm not sure if you ended up using those, but there are some existing VIs that ship with LV that you might be interested in using. Since these VIs are not in the palettes, I recommend making a copy of them for your own code... Open up <labview>\vi.lib\utility\error.llb In there you'll find VIs for getting the longest line in pixels, the height of text given an amount of space (taking word wrapping into account), etc. These are used by the General Error Handler dialog.

Thanks for being the exception to the rule, Ben.

Well I never learned that leason so being the fool that I am I went off and started pushing evnts down into the sub-VI that handle each of the modes the app runs in. I will not multiply words but I will invite you to examine the images I uploaded to the Dark-side that can be found here. This approach lets me develop sub-VI that are clean and focused on only the events that apply to the current operating mode as shown here. If you really want to rad more about this approach see this thread on the Dark-side. Ben

To extend the analogy let's replace your numerics with something vehicles have. A vehicle has an engine, and a method to "Start Engine". You've created a "car", which being a vehicle has an engine that can be started, and you've given it a second engine (!) and were surprised when the "Start Engine" method started the first engine. OK, so, why did you add a second engine? -- James BTW. The "parent/child" terminology of OO is actually confusing; "Car" is not a child of "Vehicle", it is a type of vehicle.

Sorry about that! When I downloaded Darren's VI, it went straight to my Downloads folder and was being linked from there. I've fixed that now and have actually included it this time Here is the updated R5. LabVIEW Task Manager R5.zip I've added grouping by class/library that you suggested. I've also added a Close FP button and improved the numeric sorting of the data tree. Please let me know if anything is missing this time or if you have any suggestions/comments.

My preference would be to start simple and only address the most basic, and widely useful, functionality of splitting the input string into an array of single characters. If it's determined that people would benefit from additional functionality, it can always be added later. But, we don't want to risk adding features that people won't need, since every feature must be designed, documented, tested, and maintained, which takes development resources away from other high-value features/activities.

What are the use cases for choosing random elements in an array? Personally, I've only had to do this once, and it was in an NIWeek coding challenge about 6 years ago Just thinking.... could this be further generalized to a function that chooses a random integer between two ranges (for example an array element index between 0 and Length - 1)? Maybe it would be good to add such general purpose functionality to the OpenG Random Number within Range (adding the ability to work with integers), as opposed to the more specific use case of choosing random elements in an array.

As this is being referred to in another thread, I'm updating the library to a more recent version 2.1. The library now requires LV2011. LabVIEW.Messaging.2.1-r1423-LV2011.zip