just made the transition to 2.1 (finally) and we’re pleased with
the performance improvments (and so is our client)
there’s one thing that’s been driving me nuts for a while now,
and i was hoping this would be fixed when i upgraded, but it’s
not
i call a few global methods from many of my calculations; i believe i
read in the forum a while back that this was ok to do.
the problem is that whenever debugging is enabled,
every time a calc calls a global method, the
debugger breaks on that global method, even though
there are no breakpoints enabled in it. this is really frustrating,
since it makes it almost impossible for me to use the debugger.
do you have on entry break enabled?
Please disabled that one. And only use real breakpoints to start debugging.
If you are saying that an enbled debugger (disabled debugger should of course never break) and entry break disabled and no breakpoints set in the global. It still breaks then this is something i have to look at.
If you are saying that an enbled debugger (disabled debugger should of course never break) and entry break disabled and no breakpoints set in the global. It still breaks then this is something i have to look at.
yes, that’s it exactly. it makes debugging very difficult, as
the debugger keeps popping up when i’m working.
This is also an issue for me. I’m using a global to store the current client ID. This project is designed to handle multiple clients simultaneously, each of which should only see their own records.
It becomes a real headache during development when I jump into and out of design mode – each jump loses the current value of the global. Any method that evaluates the client id breaks. I solved it by creating a separate table to store the current globals right after log in. When I jump out of design mode I run a global method that repopulates my globals. Providing that I remember to do so.
Is there a more elegant way to maintain the client ID of the current user than using a global? Is there a better way to maintain globals while in development?
I have the same issue here, when I enable the debugger, and do NOT set any breakpoint, the method stops, when I call globalmethod, that passes a value thru another method.
I have the same issue here, when I enable the debugger, and do NOT set any breakpoint, the method stops, when I call globalmethod, that passes a value thru another method.
Request for 2.1.2. The Window pulldown “remember” its state from Servoy launch to Servoy launch. Right now each time I launch Servoy Developer I’m presented with a list of forms I rarely use. The pulldown only becomes useful later in the day once I’ve jumped to all the forms I’m currently working on.
Morley: Don’t make feature request inside a thread that has nothing to do with the topic!
HJK: are you saying that you have a global method that calls a global method and that method is breaked without breakOnEntry but the debugger is enabled? (youre wheren’t stepping ??)
jcompagner:
Morley: Don’t make feature request inside a thread that has nothing to do with the topic!
HJK: are you saying that you have a global method that calls a global method and that method is breaked without breakOnEntry but the debugger is enabled? (youre wheren’t stepping ??)
No, I call, from a formmethod, the global method and that method calls another form method.
It is the code, that Jan made, with the solution that comes with the dbtreeview-bean. I copied it, one-on-one.
It is the method, that is triggered, when you click on a node-entry.
When I did that, and I had the debugger on (with no break-points) the debugger was stopping the method!