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

Flickering content in debugger panels #259

Open
ilmoralito opened this issue Apr 18, 2024 · 5 comments
Open

Flickering content in debugger panels #259

ilmoralito opened this issue Apr 18, 2024 · 5 comments

Comments

@ilmoralito
Copy link

Starting with the March 24 update, I began to notice the behavior that apparently occurs when the screen refreshes. The debugger elements disappear for a while and then appear again. I attach a video of the behavior discussed. Any hint on how to correct this. Greetings and thanks in advance

sublime-debugger.webm
@daveleroy
Copy link
Owner

With the tab/control bar on the bottom it has to disappear when it detects scrolling and come back when scrolling has stopped it will bounce up and down

@ilmoralito
Copy link
Author

Hello. Thanks for answering. I understand this is the expected behavior. In my case, the experience is that when I extend the content of some element, something like a refresh occurs and I have to do it until I can see the information I want.

@daveleroy
Copy link
Owner

daveleroy commented May 4, 2024

I'm not really sure whats happening here it kind of looks like the adapter is sending a stop event and the whole thing is refreshed.

I can't really tell what you are clicking on here. Are the variables you have expanded collapsing when it happens?

Debugger: Show Protocol would let you see if there is anything besides the variable requests going on when you expand stuff

@ilmoralito
Copy link
Author

What you describe is the experience I have when debugging. Regarding Debugger: Show Protocol I don't understand what I should do. Could you tell me how to proceed here. Greetings and thanks

@daveleroy
Copy link
Owner

Running that command from the command palette should open a second window which will get populated with logs when running a debug session

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants