LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

debug or elease ???

Hi guys,
I developed a small sw that acquire a triggered image from a camera.

With debug in cvi i have not problem, but when i run execute program, my
application break.
On title bar there is a message "application don't respond".
This happened when i move mouse or i do duble-click more times.

Any one knows what are differents of behavior between debug and release ????

Thank's
marco


0 Kudos
Message 1 of 3
(3,140 Views)

Hi Marco,

I might need some more information:

  1. which version of CVI you're using?
  2. How does the application behave (which driver calls are you using, are you using a National Instruments camera or a 3rd party device, etc..)?
  3. There are some warning or runtime errors when testing the application?
  4. Does it use user interface processing?
  5. Have you monitored the CPU and RAM consumption when the application is running in release mode?

We have to investigate deeper on the single application since the differences between debug and release mode are mostly due to the presence of debug tools (runtime error checking, breakpoints etc.)

Hope this helps,

Best Regards,

Fabio

Fabio M.
NI
Principal Engineer
0 Kudos
Message 2 of 3
(3,110 Views)
Thank's Fabio for your attenction.
I solved problem with a function that hide title bar of panel.

for your question:

-CVI 8.0
-my application run a cicle do while and in that time i acquire some picture
with 3th par driver
-no there are not warnings or errors.
-some processdrawevents() to refresh some contrul during while loop
-there are no difference of memory of cpu


Regards
Marco

"Fabio_81" <x@no.email> ha scritto nel messaggio
news:1197544211589-626143@exchange.ni.com...
> Hi Marco,
> I might need some more information:
>
> - which version of CVI you're using?
>
> - How does the application behave (which driver calls are you using, are
> you using a National Instruments camera or a 3rd party device, etc..)?
>
> - There are some&nbsp;warning or runtime errors when testing the
> application?
>
> - Does it use user interface processing?
>
> - Have you monitored the CPU and RAM consumption when the application is
> running in release mode?
>
> We have to investigate deeper on the single application since the
> differences between debug and release mode&nbsp;are mostly due to the
> presence of debug tools (runtime error checking, breakpoints etc.)
> Hope this helps,
> Best Regards,
> Fabio


0 Kudos
Message 3 of 3
(3,074 Views)