this i found in the Servoy developer Help (Java development user guide > Reference > Views > Debug View )
that would be nice if it works like this!
[attachment=1]Prtscrn_01.jpg[/attachment]
this is in the wicki 5.2 (http://wiki.servoy.com/display/SERV5/De … w+controls)
thats the pity way it works in my developer environment:
[attachment=0]Prtscrn_02.jpg[/attachment]
Ist this a question of how to set the preferences, or is it just a mistake in the documentation ?
Thanke you for a clarifying
Somehow some old pages were incorrectly available in th4e 5.0 documentation, we removed them now.
What exactly is the behavior you are talking about? The Step Over or the Step Return?
Paul
pbakker:
What exactly is the behavior you are talking about? The Step Over or the Step Return?
Paul
Sorry I was not clear:
The Step Over would be very nice (because I miss the Set Next Step ), to jump over statments
wich are troublemakers.
The reality now is, that the debugger ignores the following breakpoint in case of Step Over . This is
not very necessary, because I can turn off the breakpoints with a doubleclick anyway.
for me it doesnt ignore…
function a()
{
var z = 10;
var x = b(10);
application.output(x);
}
/**
* @properties={typeid:24,uuid:"8C2A1DC0-B3E1-4B23-9FEA-7FAA23D09F4B"}
*/
function b(y)
{
application.output(y)
return y+10;
}
if i place a breakpoint at the first line of both methods
and i start in ‘a’ and then constantly do step over, it will break in b.
set next step is possible, at least you can select a line below the current one and do CTRL-R (run to line)
(that will also break on exception that it encounters in between)
jcompagner:
if i place a breakpoint at the first line of both methods
and i start in ‘a’ and then constantly do step over, it will break in b.
Yes it’s true. So no one of the dokumentation printscreens are true.
it seems to make no difference if I “step into” or “step over”
jcompagner:
set next step is possible, at least you can select a line below the current one and do CTRL-R (run to line)
“run to a line” ist not same as “set next step”
“set next step” means for me: select any line below, then execute it with the “step into”/F5 , without
having executed the lines between.
stefanoni:
it seems to make no difference if I “step into” or “step over”
step over will step over a call, only if you have a breakpoint in it it will break there.
Step into will really always step into the method no matter what if there is a breakpoint (because you are constantly “breaking”)
stefanoni:
“run to a line” ist not same as “set next step”“set next step” means for me: select any line below, then execute it with the “step into”/F5 , without
having executed the lines between.
Thats currently impossible. (i also cant do that in java)
Would be quite weird, because the code flow would be totally different, because you could have a completely different stack of variables when you just jump over stuff.
Would be quite weird, because the code flow would be totally different, because you could have a completely different stack of variables when you just jump over stuff.
I do this weird things everyday with the VFP and it helps me a lot…
But I am quit happy til now with Servoy, an working on releasing old habits.
Thanke you for all your answers
can i ask why do you do that everyday?
just really jumping over code lines so that those are not executed?
I personally wouldnt even know when i would use that in debug. Because your whole debug session is that just invalid because what you debug is never what clients would get…
How comfortable to repeat the last 20 codelines again with manual changed variable values, or use the return(true) insted of return(false), or continue the path of an else insted of an if, or break the actual function by using the next available return and so on.
I dont want to run the code like the users usual do, but check out, with different cases, where are the problems and try to understand the wy my code runs in case of an error.
but now you are describing something else
Thats drop to frame in java (in eclipse) where you go backward in your code so that you can execute it again.
That i get, But getting forward skipping really code thats is between the current line and the next, that i never have heard of.
jcompagner:
but now you are describing something else
Now, its exactly this what i use everyday in Foxpro:
i can jump to any codeline at any time, just by set the cursor to the wished codeline, then press the button SET NEXT STEP.
Only if i want to jump into an other function i need to SET NEXT STEP to any of return of the actual function and execute it.
regards
Even though this reply is coming a little bit late, but I just want to clarify for the readers:
Even in FoxPro it is NOT possible to jump over some lines of code without executing. That relevant option in the VFP debugger means: If you are in STEP ON mode (i.e. you press F8 repeatedly to go from one line to the next), then that “Jump over” (with F6) just runs the code to that designated location without breaking at every line. It does not mean that this code would not get executed, it’s just that the debugger temporarily doesn’t stop on each line.
I agree with JCompagner that this would be really a freaking possibility. FoxPro is surely different, but not that strange
wOOdy
wOOdy:
Even in FoxPro it is NOT possible to jump over some lines of code without executing.wOOdy
I tell you it is strange
You just set the cursor where ever you want, then press SET NEXT STATEMENT (see printscreen) and
VFP executes exactly this statement next (withou executing ‘ARE YOU SHURE’, scroll down the printscreen,
to see, value of cTest is still “Hello Woody”).
[attachment=0]Prtscrn_01.jpg[/attachment]
You also can go back, do it again, jump anytime with any return out of the current function and so on…
Hi Alesandro,
hmmm. you really got me with that one… Bingo! I didn’t thought about the “Set next Statement” feature. I just was focussed at the STEP OVER button in the toolbar, since that one was mentioned in the discussion here. Or maybe I just don’t debug that much anymore
Ok, FoxPro is really strange and with lots of possibilities which other tools cannot reach (refactoring a prominent marketing splash here)
wOOdy
(feeling very embarrased that you beat me)
wOOdy:
(feeling very embarrased that you beat me)
yes, and I’m shure it’s the first time since times of “compuserve”. Between there are times I received and watched thousands
of helpfull answers from you… So lets go on for an other 20 Years… hopefully with servoy
best wishes
Alessandro
