When I debug my solution and I copy some code to paste it in the Interactive Console I doesn’t works all the time. I have to stop the client start it again and it works ’sometimes’, sometimes I also have to restart my developer.
Very very annoying when you are in the middle of debugging.
Has somebody made the same experience?
Or dose somebody have an idea why this happens.
Please create a case about this: http://www.servoy.com/s
ttmgybta:
When I debug my solution and I copy some code to paste it in the Interactive Console I doesn’t works all the time. I have to stop the client start it again and it works ’sometimes’, sometimes I also have to restart my developer.
Very very annoying when you are in the middle of debugging.Has somebody made the same experience?
Or dose somebody have an idea why this happens.
hi ttmgybta,
did you file a case for this really annoying thing (i already have it in Servoy 6) ?
I think, that we always copy/paste variable-names too, to the Interactive Console, is a workaround too,
because the actual value should be shown by the mouse-over (only the globals are shown !).
What I also don’t understand: If i run into an exception, the debug/variable windows are dead (no variables
to watch, no working Interactive Console anymore), but if I force the same error in the Interactive Console,
douring a breakpoint-stop, there are nice error-feedbacks and always the possibility to try the same statement
on and on, until it works.
greatings
stefanoni:
I think, that we always copy/paste variable-names too, to the Interactive Console, is a workaround too,
because the actual value should be shown by the mouse-over (only the globals are shown !).
i improved the mouse over now pretty much everything should be evaluated when you hover over it (there are a few cases that still don’t work but for the most part you should be able to get info from everything)
Thank you Johan,
Do you mean in Servoy greater then 6.0.0 Build 1217 ?
In this Version I can’t see the value of variables by mouseover
Example:
[attachment=0]Print_Screen_01020.jpg[/attachment]
yes i improved it and i think it will be in 6.0.2 but definitely in 6.1
just installed 6.2 . A lot of informations now on mouse over !
Thank you Johan, I am
of course in servoy 6.2 everything would be perfect! Such a nice future version we have it all
oh yeah, I’m back into the reality…
but also with the just installed 6.0.2 my live completely changed
ttmgybta:
When I debug my solution and I copy some code to paste it in the Interactive Console I doesn’t works all the time. I have to stop the client start it again and it works ’sometimes’, sometimes I also have to restart my developer.
Very very annoying when you are in the middle of debugging.Has somebody made the same experience?
Or dose somebody have an idea why this happens.
I found a workaround astounding:
if the copy doesn’t work, you just copy an past a view text inside the Interactive Console itself (just one times is enough),
after this, copy an past works again without restart the developer
do you still have a copy/paste problem then in 6.0.2?
I thought that was also already fixed. Is there still a case open?
jcompagner:
do you still have a copy/paste problem then in 6.0.2?
Yes it is still in 6.0.2.
jcompagner:
I thought that was also already fixed. Is there still a case open?
The case is filed from ttmgybta (see upper posts). Don’t know about it’s state.
But for me it’s not a problem any more, because it appears less common then
in earlier times and, as I wrote in the upper post, I just liked to share this
easy workaround.
best wishes
I created a call around the 22.07.2012 with the number (SVA:403075).
Since Servoy switch to the new Support system I can’t see it anymore!
@ Servoy: what is the stat of this Incident? And why I don’t see it anymore?
that one was closed and fixed, like i thought it was.
We did have some fixes in this area, but it seems that there is still some event/state where it still goes wrong.
Please make a new case in jira for this then if you can some how reproduce it.
P.S. Wasn’t it very good of us that we could solve/close a case already that is reported around: 22.07.2012?
I reopened the Incident from 2012
