Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debugger hides current method and buttons #238

Closed
akgrant43 opened this issue Apr 3, 2019 · 9 comments
Closed

Debugger hides current method and buttons #238

akgrant43 opened this issue Apr 3, 2019 · 9 comments
Assignees
Labels
Milestone

Comments

@akgrant43
Copy link
Contributor

The debugger doesn't size method views in the stack well, making it difficult to use:

  • It will sometimes size the current method view such that the buttons are fully visible, e.g. debug1.png, below.

debug1

  • The red underline, indicating the next message to be sent, is sometimes hidden by the buttons. In debug1,png (above), #atEnd is underlined as the next message to be sent. The stream is at the end, so stepping over it will move the highlight to the end of the method (^result). However the underline is hidden by the buttons, see debug2.png (below).

debug2

The cursor changes to an up-down arrow when it is placed over the grey drag bar at the bottom of the view, however it isn't actually possible to resize the view, so there's no way to make the highlights visible (I'll try and make an animated gif to show this).

@akgrant43
Copy link
Contributor Author

akgrant43 commented Apr 3, 2019

Short animation of not resizing the debugger :-)

DragDebugger

(yes, I am holding the mouse button down :-))

Version info:

OS: Ubuntu 16.04
gtoolkit: 2019-03-19 13:40 fd03b1f
gtoolkit-debugger: 2019-03-27 16:51 b5d353050c17c2a37094dc11c9a8d275dcc8e2f1
Pharo 7.0.2
Build information: Pharo-7.0.2+build.152.sha.890f474a81f116ead0e68c8de77790aef4e9a752 (64 Bit)

@girba
Copy link
Member

girba commented Apr 3, 2019

The method coder does not resize anymore because it is not wanted. We should remove the resizer.

@girba
Copy link
Member

girba commented Apr 3, 2019

In the first picture, I believe the problem is that method is larger than what fits in the window. At the moment, we do not resize the window. But, it should be possible to scroll to see the end of the method. Can you confirm that it's possible?

@akgrant43
Copy link
Contributor Author

In the first picture, I believe the problem is that method is larger than what fits in the window. At the moment, we do not resize the window. But, it should be possible to scroll to see the end of the method. Can you confirm that it's possible?

Scrolling causes the entire stack to move up and down. The method itself doesn't move relative to its view, so I still can't see the end of the method.

@girba
Copy link
Member

girba commented Apr 4, 2019

I am not sure I understand. Do you have a concrete case for me to reproduce it? Or maybe you just show me :)

@akgrant43
Copy link
Contributor Author

In the attached gif the highlight isn't visible under the last line (^result) (The buttons aren't hidden like in the example at the start of this issue).

My understanding from what you said is that if I try scrolling up and down, the text in the current method should scroll, so what I see is the red underline under "^result", the very end of the method. But instead the whole stack scrolls up and down.

scrolling

@girba
Copy link
Member

girba commented Apr 8, 2019

Aha. I do not think ^result should be highlighted in that method.

When the result should be highlighted it should appear like this:

Screen Shot 2019-04-08 at 6 24 56 PM

What happens if you step over once in that method?

@akgrant43
Copy link
Contributor Author

Hi Doru,

The example I gave above is from when first entering the method, so the entire method is highlighted (and "^result" should be included in that).

If I step over once the first message is highlighted:

StepOnce

(This actually raises another issue: why do I have to Step Over once to get to the first method? In Pharo 8 the first method is initially highlighted).

In the next animation, "self atEnd" will return true, so it will skip the block and highlight "^return". Unfortunately the gif software doesn't visually indicate when the mouse button is pressed, but you can see the stack top changing from "GtBuffer..." to "a ByteArray".

I Step Over once more and it returns to the calling method (DoIt):

Leaving

girba added a commit to feenkcom/gtoolkit-coder that referenced this issue Apr 11, 2019
…adding to the bottom of the coder editor to allow for highlighting to be visible. feenkcom/gtoolkit#238
@girba girba added this to the v0.6.0 milestone Apr 11, 2019
@girba girba added the bug label Apr 11, 2019
@girba
Copy link
Member

girba commented Apr 11, 2019

We now have an extra padding at the bottom of the editor, and we removed the resizer as we do not use it.

Screen Shot 2019-04-11 at 11 10 58 AM

@girba girba closed this as completed Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants