Well:
- I set some breakpoints.
- The game did stop indeed
- But it wouldn't stop at the lines the breakpoints were at, but at some other line.
The other line seems to depend on where the breakpoint originally was, because sometimes it doesn't show the debugger at all (I think that means that it's stopped at some code in the greenfoot or java package)
ok, but I mean, what is your code, where do you set the breakpoint, and where does it actually stop?
Well, it happens with all of the classes, so shall I send you the whole project? If you email me (svnigte@gmail.com), I'll respond and give the source code.
Could you just produce a small example and post the code here? Thanks. Also, is there some pattern to where you set the breakpoint and where the game stops? I.e. is it always two lines afterwards or something like that?
Sorry, I meant a small self-contained example - one that I can try myself. This sounds very strange. Does it happen in other projects or just one? Can you give a self-contained example?
Well, I don't know exactly what you mean by 'self-contained example', but how would I make something like that?
And something I just noticed, it only seems to happen with breakpoints in my class 'ScriptReader'. Shall I give you all of the code then?
Hmm, maybe just send the whole scenario (to support@greenfoot.org) with some instructions on how to reproduce it (i.e. what line to put the breakpoint on and what to do then). Thanks.
(by self-contained example I mean an example that is complete, that doesn't need other code to try out. When looking at programming problems or bug reports people will often talk about a "small self-contained example" or SSCE - because if you have a small example, it's usually much easier to track down an issue).
Thanks for looking at it! I really appreciate it, and am happy that it wasn't my fault!