forums.silverfrost.com

[sparge]

I just upgraded to v6.00 today ... anyone else done so, and been using SDBG, and observing the same behaviour as me, viz sudden unwanted ability to step through the code just as a result of moving the mouse over the Step Into and Step Over buttons, without actually clicking them? Is this:

A) some ultra-weird side-effect of my misbehaving code
B) an exciting ne v6.00 bug
C) an exciting new v6.00 feature
D) none of the above

I think I'd like to phone a friend ...

[IanLambley]

Congratulations on being the first to report a V6.00 bug - there must be a prize for that!
Ian

[sparge]

Hehe, thanks - did you reproduce it then?

[PaulLaidler]

I can confirm that there is a problem with SDBG when you move the mouse off the toolbar. I appears to trigger a mouse click (at least on some machines and on some occasions).

At the moment I don't know if this only appears in the new release.
Chances are that it is not a problem in SDBG itself but a consequence of something that has been added to ClearWin+. If this is the case then the fix will be in salflibc.dll rather than SDBG.

I will see what I can find...

[PaulLaidler]

I have tracked down this bug within the latest salflibc.dll.

It relates to the new %ib[mouse_hover] option and the fact that a MOUSE_LEAVE event is being sent to the button callback function when the mouse leaves the toolbar even though the new option is not switched on.

There are various ways to work around the problem.

1. We could make a new release of salflibc.dll available.
2. You could use a old salflibc.dll if you have one and it does everything you need.
3. If your only problem is with SDBG then you could use the Plato option of integrating Plato fully with SDBG.
4. If the problem is in your application and you want to modify your program for the short term then you will need to identify the callback reason in the callback for each of the buttons in your %ib bars.

I am sorry that this bug has slipped through. If it is any consolation, I can assure you that it was not a careless bug (if ever there was such a thing).

[sparge]

Hi Paul,

Well done for tracking it down so efficiently. Worse things happen at sea It's good to know there are so many possible workarounds. I have opted for #3 at the moment - previous difficulties with the Plato/SDBG integration notwithstanding, it seems to be working fine at the moment - and I will fall back on #2 if necessary (and if it works).

Andy

[sparge]

A little more feedback on this issue. I have reverted to using SDBG for the moment, despite the issue with the run control buttons, becaue I find it much easier to use, and apparently more powerful, when it stands alone. I presume there are ways to do everything I am accustomed to do when it is integrated with Plato, but it's easier in the hort term just to live with SDBG's new-found misbehaviour.

My purpose for posting is to say that it would be completely easy to live with this bug if it were not for another that I have just discovered. On the basis that all the three main run control buttons (Continue, Step Into and Step Over) have keyboard equivalents, in principle I just need to retrain myself to use them and to keep my mouse well away from the toolbar. Unfortunately, F6, F7 and F8 have no effect on my machine. Are they just supposed to work (my expectation), or is there a software setting, option or preference buried somewhere that needs to be frobbed?