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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dialogs and tweaks #26

Closed
wants to merge 6 commits into from
Closed

Dialogs and tweaks #26

wants to merge 6 commits into from

Conversation

fllp
Copy link

@fllp fllp commented Nov 15, 2019

Converts QML pages for adding and editing (Add.qml, Edit.qml) vocabulary into Silica Dialogs (no buttons, please 馃槈 ).

Also adds some fine tuning:

  • set focus on first entry field (word) when adding vocabulary
  • enable enter key only after text was input
  • move cursor to end of first text field (word) when editing
  • anchor contents to individual parent instead of page

New add dialog:
Add-Dialog focus-sm

Acceptable after input:
Add-Dialog-sm


Edit dialog:
Edit-Dialog-sm

Convert Page to Dialog with header and remove button
Anchor page to header to avoid clipping
Scale width to parent rather than page
Enable enter key after input only
Also put cursor at end of word when editing vocabulary
@Top-Ranger
Copy link
Owner

Thanks a lot! I'll look into it and test it.

There were two reasons why I used a button in the original design:

  1. It made Error handling easier. I could abort the whole procedure and show an error message in case something went wrong. I have to check how this works with Silica Dialogs.
  2. In earlier versions saving was sometimes a bit slow. By using a button, the feedback to the user was a better (no stuck half-changed page). I don't think that's still a problem.

For me it is important that 1. still holds true (that is, in case of any error the page is still open and thus the input is not lost). Have you tested that case?

@fllp
Copy link
Author

fllp commented Nov 17, 2019 via email

@Top-Ranger
Copy link
Owner

I've run some tests, and unfortunately I couldn't get the page to stop closing if an error occured (to test this, simply add "return false;" before this line). Because of that, I'll not merge this branch.

If anyone has an idea how to fix it, I'll be happy to merge the changes.

Thanks again for the suggestion.

@fllp
Copy link
Author

fllp commented Jan 25, 2020 via email

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

Successfully merging this pull request may close these issues.

None yet

2 participants