In RC11 I am not able to activate the debugger from the ‘Tools’ menu. Was working in RC10.
John McCann
Servoy Developer
Version R2 2.0 rc11-build 270
Java version 1.4.2_04-b05 (Windows XP)
In RC11 I am not able to activate the debugger from the ‘Tools’ menu. Was working in RC10.
John McCann
Servoy Developer
Version R2 2.0 rc11-build 270
Java version 1.4.2_04-b05 (Windows XP)
Unable to reproduce this, anyone else seen this?
yes, on one machine here happens the same. The debugger just doesn’t show up. You can manage to activate it if you set a breakpoint somewhere.
same with rc12 on this machine!
on that same machine I cannot activate the XPLookAndFeel. In the properties file nothing is written after the =-sign for the look and feel.
Is the toolbar button also not working?
is there an entry in .log.txt file after you have pressed the toolbar or menuitem?
I’m glad to hear that I am not the only one. I have also noted that I can get it to work if I set a stop point in the debugger. I can’t test the log as my developement computer went down.
John McCann
I haven’t checked the toolbar - will do that tomorrow. The debugger problem doesn’t throw anything into the log-file, though…
hitting any toolbar button is no problem… there is no log entries at all.
i don’t mean any toolbar button.
Can you open the method editor WITH the toolbar button?
yes.
In the meantime we have installed RC12 on a newly set up windows xp box: same result. No debugger.
All of the machines involved are German systems. But so is mine and there it works nicely. The only difference between my machine and the problematic ones is that 1) they have installed RC12 as the first Servoy installation and 2) they both use Java 1.4.2_04 while I have 1.4.2_03.
I hope you can find the problem…
can you test with RC13 that is just out?
But to make sure.
If you click on the toolbar button “Methods…” then the method editor opens fine
But if you do it with “Tools->Methods…” then it doesn’t open?
What happens if you use CTRL-SHIFT-M?
I am sorry that this doesn’t seem to be clear:
All of these actions work fine. What doesn’t work is the DEBUGGER. If you turn on the debugger and execute a method, no method window shows up. If you manually open a method and start it with debugger on, no step by step walk through is going on but the method is fully executed right away. The only way to get the debugger working is to set a breakpoint.
But that is the whole point..
The debugger only breaks when you set a breakpoint OR you have set on the property: enable entry break
we still have a communication problem: I know about breakpoints. The issue is this:
On my Servoy, when I turn on “enable debugger” under the tools menu and hit for example a button with a method attached, the method is shown and I can walk through step by step.
On the machines I talked about the script is simply executed without ever showing the method window. No walk through possible since no method ever came to front. The debugger simply doesn’t work. You never get to see a method window except you set at least one breakpoint in every method you want see.
The same happens with RC13.
Are you really sure that Entry break is ENABLED.?
READ my previous post.
That is the correct behaviour!!
On all those new machines the property (see preference button right besides enable/disable debugger in the method editor) “enable entry break”
on youre machine you have set that property so that it breaks on every script entry.. That is not the default behaviour (very very very annoying if you ask me)
Ok guys, I finally got it. Probably this happened because we newly installed the machines and I completely forgot that this option existed.
I am sorry to have stolen your time. Sometimes it is difficult to communicate through a media like this forum.
no problem
Steps:
-open solution
-choose tools → “methods…” menu
-choose tools → “enable debugger”
-choose “enable entry break” from option button pulldown besides stepover/stepinto/stepin buttons in scriptseditor window