Rick

QUOTE (Aristos Queue @ Sep 30 2008, 02:41 PM) I can see how that will build onto an array of parent, given an instance of child, via dynamic dispatch. But my goal is a bit different. What I want to do is essentially "find and extract" instance(s) of child XYZ from an array of parent, via dynamic dispatch. I currently have this working via brute force downcast type-testing, but I had hoped to use a more elegant solution.

QUOTE (Aristos Queue @ Sep 26 2008, 02:02 PM) I have a question regarding a specific use of dynamic dispatch that is related to this discussion: I want extract only one specific child class (call it XYZ) from an array of parent class, populated with multiple different sibling children classes. Is it possible in some way to use a dynamic dispatch parent method that is overridden by *only* a method of child class XYZ and use that dynamic dispatch strategy in a loop on the parent class array so that I end up with only the child object XYZ? I can easily envision ending up with an array of parent objects intermixed with my child XYZ object, but I am looking for a way to avoid type-testing altogether. Any hints/suggestions very appreciated. -Rick

QUOTE (Antoine Châlons @ Sep 10 2008, 01:59 AM) I third this! Votes++ An intrinsic tool that encourages (coaxes?) users/devs to document code is long overdue. Plus, it would solve the current auto-cleanup shortcoming regarding documentation placement.

QUOTE(Tomi Maila @ Mar 14 2007, 12:23 PM) Could you elaborate on this? Do you have other info? I *hope* there will be updates to LV8.2, but this info came from an NI rep....

QUOTE(JohnRH @ Mar 13 2007, 04:11 PM) For what it's worth, I spoke with an NI app engineer trying to recover from the bug-induced: "bookkeep.cpp", line 887 error (mentioned elsewhere on this forum; more below) , yesterday. During that conversation I asked about the eminent quarterly service release (shipping very soon) and was told that there are NO LabVIEW-related fixes in this service release. The primary update being NI-DAQmx 8.5. BTW, my fix for the bookkeep.cpp error was indeed (following the advice from this forum) to force the mass recompile by holding ctl-shift while clicking the run button. I believe this was caused when a typedef mysteriously lost it's link to the custom typedef control (it became greyed-out) and I couldn't get it to relink properly. NI is aware of this bug and noted that all reports of it had in common the use of dynamic-dispatch terminals in the project... Rick

QUOTE(Herbert @ Mar 7 2007, 03:59 PM) Thanks, Herbert. Of course that did it and it was a very simple fix. Thanks, this viewer just became much more useful to me! I figured that the use of variant was the reason that the properties tab was working, but didn't know the NI_ChannelLength value was U64. Since you seem to be the author of this fine utility, here come a feature request: It would be great if there was the NI-supported, intrinsic ability to view the data in an vector X vs. vector Y format, rather than waveform only. One obvious use of this would be plotting processed frequency domain data against a frequency vector. This would take the usefulness of this utility to the next level. Thanks again for the support! Rick

QUOTE(Herbert @ Feb 21 2007, 09:22 PM) Herbert, Thanks for the good info and acknowledgement of outstanding bugs vs. expected behavior. I've found another problem with the TDMS File Viewer that I'd like to throw out there: The TDMS File Viewer doesn't load group/channel values that contain very large value length (haven't tried determining the failure limit) data arrays/waveforms. I've written a DAQ application that streams time data to disk and also makes that raw time data available to post processing routines, the output of which is appended to the same TDMS collecting the streamed raw time data. In my case, the streamed time data can easily contain well over 100,000 continuous time data points. In trying to use the TDSM File Viewer to inspect my data file, I find that all the groups/channels entries and data is there. But, the data values are tabulated and graphed (as inspected using the tab control) ONLY for all of my post processed channel groups which contain ~20,000 data points. For the raw streamed time data channel group, the "Properties" tab lists correct information (including e.g. Property name=NI_ChannelLength with Property value=327680), but the "Values (table)" tab & "Analog values (graph)" tabs contain no data. With some inspection, I've traced this to the "Get TDMS Properties" primitive (in the "loadAndFormatValues.vi" ) that is returning info on the "NI_ChannelLength" property name. It seems this property is found, but that this length is returned as 0 (zero) for sufficiently large data sets. This is especially strange since the data length is correctly indicated as 327680 in the "Properties" tab. Is this a known fundamental limit of the "Get TDMS Properties" primitive? Thanks, Rick