Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

Moving the IntensityGraph cursor freezes out all other form activity

Unfortunately my latest idea for solution turns out to be not workable - it doesn't scale when we increase the graph history / lower the update rate. The speed of the cursor update becomes unacceptably slow at the lower update rates. I'm back to square one.

 

Thanks for the tip about the Idea Exchange, will post a product suggestion there. 

0 Kudos
Message 11 of 18
(1,699 Views)

Were you able to track down the reasons why the code I provided was causing ill side effects? My mistake for not actually linking to the Idea Exchange.

 

Cheers,

KyleP
Applications Engineer
National Instruments
0 Kudos
Message 12 of 18
(1,689 Views)

You can see the nature of the side-effect as follows. Start the debugger on the last project you sent me (that uses System.Timers.Timer). While it's running, open some other application window on your PC (PDF file viewer, whatever) so that it is covering the running Form1 application. Now minimize that other app window. You should see that the scattergraph still holds the image of the other app window. It goes away when you click into the Form1 / scattergraph.

0 Kudos
Message 13 of 18
(1,686 Views)

Hmm, I was not able to reproduce that behavior. I tried a PDF viewer as well as other applications but nothing seemed to interfere with the scatter graph. I wonder if it is an issue with your machine's performance? Try running it on a different computer if possible and see if it's replicated.

 

Cheers,

KyleP
Applications Engineer
National Instruments
0 Kudos
Message 14 of 18
(1,673 Views)

I'll give it a try on a few other machines. Can you tell me about the machine you used for this test? (XP / Windows7, CPU, memory, ...)  Thanks.

0 Kudos
Message 15 of 18
(1,667 Views)

Hi jble,

 

I gave Kyle's Timer based application a shot and very briefly see the contents of the window (much less than 1 second) before the graph refreshes, so I do not see the persistent rendering problems either. I am using a Windows 7 machine and performed the tests in Visual Studio 2008 + Measurement Studio 2010 and Visual Studio 2010 + Measurement Studio 2012.


Milan
0 Kudos
Message 16 of 18
(1,654 Views)

OK, thanks for letting me know the PC is running Windows 7. Would you mind also sharing the CPU type/speed and amount of RAM? Just so that I can try to run it on a similar machine on my end. Thanks.

0 Kudos
Message 17 of 18
(1,651 Views)

Hi jble,

 

I am running a computer with 4GB of memory (2GB free) and Dual Core 2.8 GHz cpu but it is very unlikely that a computer will need specs that high to run the sample application.


Milan
0 Kudos
Message 18 of 18
(1,640 Views)