Verbose mode

[cyro]

I'm using LVOOP very often and the bigger the code gets the slower LV reacts / works. A small change in the class-control results in minutes of waiting with no feedback. In general it would be nice to get a message box telling me what labview is doing with specific information which file and how many files are in the queue to handle so I can decide to do sth else than watching the windows circle or killing labview using the taskmanager.

My suggestion to solve this is adding a verbose mode so I can choose if I want information or not or I want the information only when 10 or more seconds passed without reaction.

It doesnt matter if LV needs more time by using this verbose mode, the point is I want to know if i have to wait another 30 seconds, minutes, hours or days... or if I should kill LV and start over again....

Thanks 🙂

[Mr.Mike]

Yes this is a valid idea.  But you should definitely get in touch with your sales rep and do the following:

1. Have them help you figure out why it's taking so long
2. Have them file a bug with NI R&D if there's no good reason for it.

[AristosQueue (NI)]

And a reminder: R&D really and truly DOES NOT MIND if you give them a bug report with a gigantic VI hierarchy attached to it. Some people don't file bug reports because they cannot isolate the bug themselves. That's R&D's job -- yes, we prefer to get a bug report with a tidy small reproducible case attached to it, but please don't hesitate to submit a report with a larger attachment. It's the only way some bugs get reproduced.

[gbecker]

I have seen this several times, too.

Usually I check with ProcessExplorer if the LabVIEW.exe is "doing" something (e.g. the evil qsort)...

and/or if the LabVIEW_32_11.0_user_cur.txt is reporting anything useful like:

06.02.2012 18:04:23.180
DWarn 0xDE90B5AC: typeprop caused typeprop a third time! Give up on: [LinkIdentity "OGData.lvclass:GetDVR.vi" [ My Computer]
e:\builds\penguin\labview\branches\2011\dev\source\diagram\proptype.cpp(756) : DWarn: typeprop caused typeprop a third time! Give up on: [LinkIdentity "OGData.lvclass:GetDVR.vi" [ My Computer]
minidump id: 4a69147d-995a-4bf8-85f4-b4bc3c94928e
$Id: //labview/branches/2011/dev/source/diagram/proptype.cpp#28 $
0x006A8973 - LabVIEW <unknown> + 0
0x10015F30 - mgcore_SH_11_0 <unknown> + 0
0x00B8D450 - LabVIEW <unknown> + 0
0x00B8D0C9 - LabVIEW <unknown> + 0
0x00B8D81E - LabVIEW <unknown> + 0
0x005C024C - LabVIEW <unknown> + 0
0x005BDA6C - LabVIEW <unknown> + 0
0x005BE11B - LabVIEW <unknown> + 0
0x005BFDF2 - LabVIEW <unknown> + 0
0x0065537E - LabVIEW <unknown> + 0
0x01636383 - LabVIEW <unknown> + 0
0x0163775F - LabVIEW <unknown> + 0
0x0163A9B4 - LabVIEW <unknown> + 0
0x00B8D7E0 - LabVIEW <unknown> + 0
0x009565C9 - LabVIEW <unknown> + 0
0x005BE004 - LabVIEW <unknown> + 0
0x005BFE34 - LabVIEW <unknown> + 0
0x01B03C84 - LabVIEW <unknown> + 0
0x01BA2A75 - LabVIEW <unknown> + 0
0x01AF804C - LabVIEW <unknown> + 0
0x01B22C18 - LabVIEW <unknown> + 0
0x01BA2069 - LabVIEW <unknown> + 0
0x01B21E69 - LabVIEW <unknown> + 0
0x0044A530 - LabVIEW <unknown> + 0
0x0044A7CD - LabVIEW <unknown> + 0
0x0044A840 - LabVIEW <unknown> + 0
0x01CA2FE5 - LabVIEW <unknown> + 0
0x74F9F13C - kernel32 <unknown> + 0
0x7740D819 - ntdll <unknown> + 0
0x7740DA2B - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x00400000 ***
#** prop types: "__________\Host\OnlineGUI\Classes\OGData\Methods\GetDVR.vi"
GoDoit: VI "OGData.lvclass:GetDVR.vi" (__________\LV2011\Host\OnlineGUI\Classes\OGData\Methods\GetDVR.vi), HeapClass "FPHP", Act 50,
GoDoit: VI "OGData.lvclass:GetDVR.vi" (__________\LV2011\Host\OnlineGUI\Classes\OGData\Methods\GetDVR.vi), HeapClass "FPHP", Act 50,
GoDoit: VI "OGData.lvclass:GetDVR.vi" (__________\LV2011\Host\OnlineGUI\Classes\OGData\Methods\GetDVR.vi), HeapClass "FPHP", Act 50,
#** prop types: "__________\Host\OnlineGUI\Classes\OGData\Methods\GetDVR.vi"
*** End Dump ***

Then I'll wait - otherwise "taskkill /F /IM labview.exe"

Being more verbose, especially during "apply changes" of classes/typedefs and during application building while processing lvlibs would be most important IMHO.

[Darren]

Any idea that has received less than 5 kudos within 5 years after posting will be automatically declined.