PureBasic Forums - English

Hello,

I wanted to point out a problem I've been seeing for as long as I can remember (since 2004? maybe it's been there since the beginning?).
Perhaps it has already been reported?
Maybe there's a good reason for it?

I've decided to report it today. Who knows why?

It's a issue that occurs in 'Standalone GUI debugger' mode and not in 'Integrated IDE debugger' (I've never tested in console mode).

The code: First compile in 'Integrated IDE debugger' mode
Point the cursor at the variable name 'Variable' on each Debug line.
Each time, the value of 'Variable' is displayed in a tooltip.

Now compile in 'Standalone GUI debugger' mode and repeat the pointing operations.
On the second Debug line, no tooltip is displayed in English GUI or a message 'Variable introuvable' is displayed in French GUI.

Of course, the order of compilation modes has nothing to do with this problem.

Voilà.

I use the standalone debugger almost exclusively since originally getting used to it when using jaPBe.

I get no tooltip with the variable's value without using calldebugger to stop the execution, otherwise it runs to the end and no values are available after that because they're all freed. This is true with either the stand alone or integrated debugger.

In the situation where automatic display of the value doesn't happen when it is pointed at I highlight the variable and all works as it did before.

Hello Demivec,

Demivec wrote: I use the standalone debugger almost exclusively since originally getting used to it when using jaPBe.

Ahhh JaPBE!!! A remarkable job with some very interesting featurers. I also used it as long as it was kept up to date and compatible with PB version (< 5.00). And then, step by step, the PB IDE caught up...

Personally, I don't remember how I started using GUI mode, maybe the default mode during installation? Was it the habit with VBA environment that I was using for work ? And since then, it's a habit that's stayed.
 

I get no tooltip with the variable's value without using calldebugger to stop the execution, [...]

No need to use Calldebugger to stop the execution, a bug is enough! And, with me, it happens often!