LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

browsing variable declaration while in release configuration

when using 'go to definition' while in release configuration, CVI gives an error telling: "Browse information is not available in the release configuration". why is it ?

browse informations are data which are constructed at compile time and stored in a file separate from the output of the compiler. i can't see the reasoning behind not constructing browse informations when in release configuration: we are compiling so we don't care about compilation time, browsing identifier is done when editing the code and not when executing it, informations about identifiers are still in the source file even in release configuration... i don't know, i can't understand this limitation.
0 Kudos
Message 1 of 4
(3,980 Views)
Hi dummy_decoy,

You make a valid point there and I agree that we should have made the browser information available in release mode but unfortunately we didn't. Our current implementation of the browser information feature is purely based on the debug information which is only available when in debug configuration.  Honestly, it's not the best implementation and I do believe it should be changed at some point. Therefore I would encourage you to submit a product suggestion so that we have this request on record. 

Best Regards,
Jonathan N.
National Instruments
0 Kudos
Message 2 of 4
(3,929 Views)
I'm down with dummy on this one.

Providing a symbol table is pretty much all it takes to do this.

Most IDE's can do it, just not CVI.

How about Jonathan just turn this one in on our behalf.

Menchar
0 Kudos
Message 3 of 4
(3,919 Views)
i filed the suggestion this afternoon. i hope it will be implemented soon...
0 Kudos
Message 4 of 4
(3,904 Views)