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

Entry: while adding text beyond visible region there is no auto-scroll #912

Closed
Aukstkalnis opened this issue Apr 28, 2020 · 4 comments
Closed
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@Aukstkalnis
Copy link

Describe the bug:

I add text at the bottom of text wedget, then pres enter, then write, and there is no autoscroll. The text is bellow the visible field. I think this is a bug, because when writing, user do not need to manually scroll down to see what is written.

To Reproduce:

Steps to reproduce the behaviour:

  1. Go to fyne_demo
  2. Click on Wiggets
  3. Click on Text
  4. Hit enter until the text reaches the bottom
  5. See that text are gone and no autostroll was made.

Device (please complete the following information):

  • OS: Windowns
  • Version: 10
  • Go version: 1.14.2
  • Fyne version: 40c918d
@andydotxyz
Copy link
Member

Quite right. This is a flaw in the current scrolling of the Entry widget that needs to be addressed.
Unfortunately the underrlying work is a breaking change and so we can't address it in a feature release, and it will have to wait until 2.0 later in the year. Depends upon #471

@andydotxyz andydotxyz added the bug Something isn't working label Apr 28, 2020
@andydotxyz andydotxyz changed the title fyne demo: scroll: while adding text in the text widget there is no auto-scroll Entry: while adding text beyond visible region there is no auto-scroll Apr 28, 2020
@Aukstkalnis
Copy link
Author

Ok, but I think for demo you just need to add simple workaround to just move scroll container when cursor is bellow the visible field.

@andydotxyz
Copy link
Member

I don't think that our demo should be including workarounds, we need to fix this properly.

@andydotxyz
Copy link
Member

Going to close this as a duplicate, we will work through Entry and other Text handling improvements in 2.0 following #471

@andydotxyz andydotxyz added the duplicate This issue or pull request already exists label Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants