swingtan
October 29th, 2008, 04:11 PM
I'm pretty sure I'm not the only one that gets these, and historically there are a few posts mentioning these error messages.....
http://farm4.static.flickr.com/3162/2985190239_c75ceb1fdc_o.jpg ("http://www.flickr.com/photos/swingtan/2985190239/" )
http://farm4.static.flickr.com/3144/2986045774_fb46057d9b_o.jpg ("http://www.flickr.com/photos/swingtan/2986045774/" )
These are not new for me, in fact the first image was taken on the 16th Sept, the second today. they have been occurring for quite a while and while they can be annoying, they never seemed to cause any real problems. However I was a bit worried and would always restart the application if one of these errors occurred.
Today I had a bit of a breakthrough in that I worked out the exact scenario that causes this to occur.....
Start Tune Tool or Scan Tool and then minimise the application.
Leave it minimised for some time while continuing to use the laptop for other work.
After some time ( which can take a while ) maximise Tune Tool or Scan Tool and immediately hover the mouse over a button.
As the Tool attempts to find the pop up "help bubble" for that button, the error occurs.
You can minimise the Tool and maximise it again, but the error occurs every time you hover the mouse over a button.
In Tune tool, if you then select a new parameter field to adjust, everything resets and you get the "help bubbles" back and no more errors.
In Scan Tool, if you open the DVT tab up and attempt to activate, the issue clears and again you can get the "help bubbles" back with no errors.
So this leads me to think that there is something funny occurring when the application attempts to call the routing that activates the "help bubble" / "button prompts" ( or what ever they are called ). Has any one else noticed this? My laptop is fairly unique in that it does a lot more than just tuning and rarely gets shut down. Most of the time I simply "sleep" the laptop when I'm not using it so it does have periods of time where it may go a week or 2 without a reboot ( amazing for Windows.... ). However, it did get a reboot last night so should be in a fairly good state.
Simon.
http://farm4.static.flickr.com/3162/2985190239_c75ceb1fdc_o.jpg ("http://www.flickr.com/photos/swingtan/2985190239/" )
http://farm4.static.flickr.com/3144/2986045774_fb46057d9b_o.jpg ("http://www.flickr.com/photos/swingtan/2986045774/" )
These are not new for me, in fact the first image was taken on the 16th Sept, the second today. they have been occurring for quite a while and while they can be annoying, they never seemed to cause any real problems. However I was a bit worried and would always restart the application if one of these errors occurred.
Today I had a bit of a breakthrough in that I worked out the exact scenario that causes this to occur.....
Start Tune Tool or Scan Tool and then minimise the application.
Leave it minimised for some time while continuing to use the laptop for other work.
After some time ( which can take a while ) maximise Tune Tool or Scan Tool and immediately hover the mouse over a button.
As the Tool attempts to find the pop up "help bubble" for that button, the error occurs.
You can minimise the Tool and maximise it again, but the error occurs every time you hover the mouse over a button.
In Tune tool, if you then select a new parameter field to adjust, everything resets and you get the "help bubbles" back and no more errors.
In Scan Tool, if you open the DVT tab up and attempt to activate, the issue clears and again you can get the "help bubbles" back with no errors.
So this leads me to think that there is something funny occurring when the application attempts to call the routing that activates the "help bubble" / "button prompts" ( or what ever they are called ). Has any one else noticed this? My laptop is fairly unique in that it does a lot more than just tuning and rarely gets shut down. Most of the time I simply "sleep" the laptop when I'm not using it so it does have periods of time where it may go a week or 2 without a reboot ( amazing for Windows.... ). However, it did get a reboot last night so should be in a fairly good state.
Simon.