> Thank you. This kind of detailed feedback is very useful. I
> will try to correct the problems you have noted.
>
:)
I have some more bugs for you. ;)
* If I debug Foo.java (i.e. the '=>' symbol is currently in Foo.java) and you
switch to some other buffer containing Java code and then try to single step,
then JDEbug does not like that situation very much at all.
I suggest that I should be transfered back to the correct buffer (i.e.
pop-to-buffer or something) and to the correct position in the buffer (i.e. to
the line where the '=>' symbol is).
If I have several debugging sessions running at the same time, it would be nice
to get a pop up window (or something) listing the buffers where debugging
sessions are currently running. Selecting one of the buffers should then
transfer me to that buffer etc.
Another approach would be to just make the correct buffer visible and not move
the focus from the current buffer.
* Set a breakpoint. Copy some code. Place point on the breakpoint and paste it
in. The new text will be colored as the breakpoint. If the breakpoint is cleared
all the coloring is removed.
This one is more like a feature request. I think that if any of the JDEbug
buffers are selected, the JDEbug menu should not disappear (or atleast the
keybindings should not disappear).
This happens frequently when you use the tree list in the local variables
buffers.
Perhaps you should not transfer focus if you are located in any of the JDebug
buffers? The assumption would then be that you want to stay in the buffer (for
instance the local variables buffer) and continue to do things.
What do you all think? What is the correct way of solving this?
/John
--
LM/ERA/LVA/KD John Olsson mailto:[EMAIL PROTECTED]
Ericsson Radio Systems AB, Box 1248, S-581 12 Linkoping
-------------------------------------------------------------
Phone: +46 13 321070 ECN: 868 1070 Fax: +46 13 287370
-------------------------------------------------------------
I was doing object-oriented assembly when I was 1 year old...
For some reason my mom insists on calling it "Playing with blocks"
