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

make dialogs modals #152

Closed
wants to merge 2 commits into from
Closed

make dialogs modals #152

wants to merge 2 commits into from

Conversation

bootsa
Copy link

@bootsa bootsa commented Aug 2, 2019

make the file and message pop ups modals (children of the main window) so that they don't open up a second app instance/dock icon (at least in Linux, haven't test Windows or MacOS), and stay on top of the main window preventing getting lost confusingly behind main window.

Disables main window when dialogues are open - can't think of a time when you wouldn't want this.

make the file and message pop ups modals (children of the main window) so that they don't open up a second app instance/dock icon (at least in Linux, haven't test Windows or MacOS), and stay on top of the main window preventing getting lost confusingly behind main window.

Disables main window when dialogues are open - can't think of a time when you wouldn't want this.
@bootsa
Copy link
Author

bootsa commented Aug 3, 2019

Oops, missed the open refactor PRs (#127, #128 & #129) that actually implement this. Would be nice to have them resolved.

@bootsa bootsa closed this Aug 3, 2019
@juancarlosfarah
Copy link
Member

@bootsa, you can now resume this as #127, #128, and #129 are now in master.

bootsa pushed a commit to bootsa/graasp-desktop that referenced this pull request Aug 28, 2019
make os dialogs (open, save, etc) modal so they appear above main window and not as a separate window.

fixes graasp#152
@bootsa
Copy link
Author

bootsa commented Aug 28, 2019

Sorry, been away for a couple of weeks.

Not sure if I submitted it correctly as I did it on another branch and referenced here. Does that work or do I need to create another pull request?

@juancarlosfarah
Copy link
Member

Hi @bootsa, you've correctly fixed the conflicts, but you've overridden your changes. We can either (1) close this PR and you can do your changes in a fresh new one. Or (2) you can add your new changes to this PR.

I would prefer option (1).

@bootsa bootsa mentioned this pull request Aug 28, 2019
@bootsa
Copy link
Author

bootsa commented Aug 28, 2019

Hi @juancarlosfarah,

Oops! OK, have now created a new pull request #182

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.

2 participants