topic Re: Control the speed of the Debugger in QlikView

Control the speed of the Debugger

datanibbler — Mon, 20 Oct 2014 10:51:59 GMT

Hi,

I have been spending much of last week running my code in Debugging_mode over and over again.

I have noticed that going through the code step-by-step is a good way to identify any issues - but once you have made sure a particular piece of code is all right, then it gets kind of tiring to do that until you get to the point where you want to look close...

This brought up the question: Wouldn't it be possible to conttrol the debugger insofar as the code just runs through up to a certain point and just stops there - without exiting, though - and you take it stepwise from there?

Best regards,

DataNibbler

Re: Control the speed of the Debugger

ThornOfCrowns — Mon, 20 Oct 2014 11:00:02 GMT

You can set a breakpoint in the debugger which does exactly that.

Re: Control the speed of the Debugger

tresB — Mon, 20 Oct 2014 11:03:09 GMT

Perhaps this:

In the debug mode, click on line number to set 'Break Point'. Click on Run to reach there, and then use Step for detailed view slowly.

Red dot denotes the breaking point here.

Re: Control the speed of the Debugger

datanibbler — Mon, 20 Oct 2014 11:08:02 GMT

Hi,

I just read about that and I tried it. It doesn't yet seem to work though.

I can click there and I get that red dot allright - but when I click on "Run", the script runs right up to the EXIT SCRIPT, not stopping at my breakpoint ...

Re: Control the speed of the Debugger

tresB — Mon, 20 Oct 2014 11:12:54 GMT

Sorry, missed a part. Try this sequence:

-Set the break piont

-Click once on Step

-Click on Run

Re: Control the speed of the Debugger

ThornOfCrowns — Mon, 20 Oct 2014 11:58:24 GMT

The debugger is a bit hit and miss when it comes to setting breakpoints - I normally set a TRACE line in the code and set the breakpoint there, just to be sure.

Re: Control the speed of the Debugger

datanibbler — Thu, 23 Oct 2014 11:05:56 GMT

You're right. On the day when I set a breakpoint, it didn't stop there - never on that day - so I didn't think of removing it. Now, a few days later, it suddenly started working - even without first clicking on "step" - I clicked on "run" and it stopped right there and waited for my input.