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

[guilib] fix modality handling of dialog slider (fixes #16140) #7571

Merged
merged 1 commit into from
Jul 22, 2015

Conversation

xhaggi
Copy link
Member

@xhaggi xhaggi commented Jul 21, 2015

As reported at http://trac.kodi.tv/ticket/16140 the slider dialog does not work if it's used as overlay. This happens because we only support one modality type per dialog and the slider dialog is the only one which breaks this rule and is used as modal and overlay at the same time.

This PR will fix the issue by setting the modality type at runtime depending on the use-case.

@UniversaI it would be nice if you could confirm that it works
@mkortstiege mind taking a look

@xhaggi xhaggi added the Type: Fix non-breaking change which fixes an issue label Jul 21, 2015
@un1versal
Copy link
Contributor

Give me a while Its compiling this now.

@xhaggi
Copy link
Member Author

xhaggi commented Jul 21, 2015

sure no rush i never used that feature 😃

@un1versal
Copy link
Contributor

@xhaggi Pulled this PR ontop of master and the issue is still there.

I dindt pull https://gist.github.com/mkortstiege/026fa815e2d8f9461967 in addition to yours which fixed the repeat keypress was I suppose to compile both?

@xhaggi
Copy link
Member Author

xhaggi commented Jul 21, 2015

no only this PR please, i'll take another look at it.

@xhaggi xhaggi force-pushed the fix-modality-of-dialog-slider branch from e17181a to 732430d Compare July 21, 2015 14:00
@xhaggi
Copy link
Member Author

xhaggi commented Jul 21, 2015

@UniversaI i've updated the PR, please do another test, thanks.

@xhaggi
Copy link
Member Author

xhaggi commented Jul 21, 2015

I'm not really happy with this fix, because IMO we should introduce a new dialog for the case we need it as an overlay. This way we have a cleaner implementation and a skinner could style the overlay different from the modal (the modal should hold an ok and close button).

@mkortstiege @ronie what's your opinion?

@un1versal
Copy link
Contributor

@xhaggi Confirmed fixes issue. 💃

Congrats and thank you :)

@mkortstiege
Copy link
Member

Why not use my gist in case it fixes the issue? The slider should be handled just as the other osd/overlay Dialogs.

@ronie
Copy link
Member

ronie commented Jul 21, 2015

skinners prefer less dialogs, not more ;-)

why not make this dialog modal all of the times?
is there any current usecase where it really should be modeless?

@un1versal
Copy link
Contributor

Why not use my gist in case it fixes the issue?

Your gist fixes the issue but when you go into OSD manually and select any slider then it stays on screen forever, so it fixes the issue and breaks other use cases, the way @xhaggi did it works in any case.

@xhaggi
Copy link
Member Author

xhaggi commented Jul 21, 2015

@ronie imo it's a design flaw to unify a modeless and modal dialog. if you want to add a button to close this dialog this won't work in the modeless mode. making this dialog only modal will break the case @UniversaI described. same happens if we make it modeless as suggested by @mkortstiege. we can't take care of what skinners want (less dialogs) if this breaks our internal design. sure this worked for years but only with some limitations like i previously said (no buttons to interact).

@xhaggi
Copy link
Member Author

xhaggi commented Jul 22, 2015

jenkins build this please

xhaggi added a commit that referenced this pull request Jul 22, 2015
[guilib] fix modality handling of dialog slider (fixes #16140)
@xhaggi xhaggi merged commit 7ab70c3 into xbmc:master Jul 22, 2015
@MartijnKaijser MartijnKaijser modified the milestone: J**** 16.0-alpha1 Jul 23, 2015
@xhaggi xhaggi deleted the fix-modality-of-dialog-slider branch August 6, 2015 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Fix non-breaking change which fixes an issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants