When using RetroRunner, this helps ensuring we unload the game, deinit
the core, and by extension that cores saving on unload save as expected
when quitting the application.

https://bugzilla.gnome.org/show_bug.cgi?id=782772

Check that the inhibition cookie isn't 0 before using it in
ApplicationWindow.uninhibit(), this avoids a runtime error message.

https://bugzilla.gnome.org/show_bug.cgi?id=781886

Replace mention of GPLv3 by GPL-3.0+ as initially intended in the file
headers.

https://bugzilla.gnome.org/show_bug.cgi?id=781036

https://bugzilla.gnome.org/show_bug.cgi?id=779780

Save the size of the window in the gschema and retrieve this parameter
to automatically set it back.

https://bugzilla.gnome.org/show_bug.cgi?id=779095

Save whether the window is maximized or not in the gschema and retrieve
this parameter to automatically set it back.

https://bugzilla.gnome.org/show_bug.cgi?id=779095

Save whether the games shoud be in fullscreen or not in the gschema and
retrieve this parameter to automatically set the games fullscreen.

https://bugzilla.gnome.org/show_bug.cgi?id=778236

Prevent the window to be set fullscreen when using the shortcuts on a
game which doesn't support support fullscreen in Games' window.

Ensure the error page is in a good state when displaying an error.

https://bugzilla.gnome.org/show_bug.cgi?id=778774

Also display the returned message on the error display page.

This helps the users to better understand why their game doesn't run.

https://bugzilla.gnome.org/show_bug.cgi?id=778773

Add a secondary label to the ErrorDisplay, this will be used in the next
commit to display a message describing the error.

https://bugzilla.gnome.org/show_bug.cgi?id=778773

Abhinav Singh authored Feb 02, 2017 and Adrien Plazas committed Feb 02, 2017

Set 'show-menubar' false in code because xml property isn't working.

https://bugzilla.gnome.org/show_bug.cgi?id=771683

Abhinav Singh authored Jan 31, 2017 and Adrien Plazas committed Jan 31, 2017

Add an overlayed revealable notification over collection icon view box.

https://bugzilla.gnome.org/show_bug.cgi?id=773882

This avoids the display part of the UI to be in an inconsistent state if
we couldn't get the game's runner.

https://bugzilla.gnome.org/show_bug.cgi?id=771513

Mathieu Bridon authored Aug 17, 2016 and Adrien Plazas committed Sep 15, 2016

This allows notifying the user when they try to logout that a game was
running, giving them a chance to cancel the logout, go back to the game,
save their progress, play for an hour or two because they got caught
back in, save their progress again and then finally logout.

This also handles poweroff, since it first logs out.

https://bugzilla.gnome.org/show_bug.cgi?id=769968

Mathieu Bridon authored Aug 31, 2016 and Adrien Plazas committed Sep 15, 2016

This makes the code a bit more flexible, introducing a new parameter to
the (un)inhibition functions, which will allow taking/releasing other
kinds of inhibitors than just the idle one.

https://bugzilla.gnome.org/show_bug.cgi?id=769968

Mathieu Bridon authored Aug 16, 2016 and Adrien Plazas committed Sep 15, 2016

Nobody wants their screen to blank and lock while they are playing.

With this change, we now inhibit the screensaver when the user is
playing a game, and the window is focused.

https://bugzilla.gnome.org/show_bug.cgi?id=769968

Check that there is no 'Quit' dialog before updating the pause when the
toplevel focus changes.

This avoids unpausing the game when dragging the dialog.

https://bugzilla.gnome.org/show_bug.cgi?id=770426

Check that there is no 'Resume' dialog before updating the pause when
the toplevel focus changes.

This avoids unpausing the game when dragging the dialog.

https://bugzilla.gnome.org/show_bug.cgi?id=770426

Avoid the 500 milliseconds delay before pausing when the toplevel focus
is completely lost.

https://bugzilla.gnome.org/show_bug.cgi?id=770426

Add a 500 milliseconds delay before pausing the game when the
application lost the focus.

This avoids annoying pauses when the shell briefly takes the focus (when
changing the sound volume for example) while avoiding to loose control
of the game for too long.

https://bugzilla.gnome.org/show_bug.cgi?id=770426

Add the Ctrl+F and F11 key bindings to toggle fullscreen and add the
Escape key binding to restore the window.

https://bugzilla.gnome.org/show_bug.cgi?id=769438

Add the handle_collection_key_event() method to ApplicationWindow to
handle collection specific key bindings.

This will help to make the code easier to read as more key bindings are
going to be added in the next commit.

https://bugzilla.gnome.org/show_bug.cgi?id=769438

This will be used by multi-source games for changing the source in the
middle of the game.

This is part of a series of commits to add multi-source support.

Pause or resume the game when the window gains or looses toplevel focus rather than when the window's state changes.

This avoids bugs not resuming the game when quickly switcing back to the
window with Alt+Tab.

https://bugzilla.gnome.org/show_bug.cgi?id=770142

Also resume it when the window gets the focus back.

This avoids the player to loose control over the game.

https://bugzilla.gnome.org/show_bug.cgi?id=770011

This allows to release the Libretro cores when quitting a game.

https://bugzilla.gnome.org/show_bug.cgi?id=770004

This avoids keeping unused runners, which is useless, make use of more
memory.

https://bugzilla.gnome.org/show_bug.cgi?id=770004

This make it more readable and hence maintainable.

https://bugzilla.gnome.org/show_bug.cgi?id=770004

https://bugzilla.gnome.org/show_bug.cgi?id=769993

When an error occurs when running a game, displays the error in a
RunError widget rather than an info box.

This displays errors in a much nicer way.

https://bugzilla.gnome.org/show_bug.cgi?id=769801

Mathieu Bridon authored Aug 14, 2016 and Adrien Plazas committed Aug 16, 2016

Sometimes, resuming the saved state of a game won't work, because the
snapshot will be corrupted.

When that happens, we now inform the user that something went wrong, and
offer them to restart the game from the main menu.

https://bugzilla.gnome.org/show_bug.cgi?id=769938

Mathieu Bridon authored Aug 15, 2016 and Adrien Plazas committed Aug 15, 2016

The player just asked us to start a game, why would they want to cancel?

This seems like such a rare use-case that we don't need a button here,
especially as there's a workaround: they could just resume, and click
the back arrow to get back to the home page.

This makes the resume dialog less heavy, as it felt very crowded with 3
buttons for just a short line of text.

https://bugzilla.gnome.org/show_bug.cgi?id=769924

This avoids a compile time warning.

https://bugzilla.gnome.org/show_bug.cgi?id=769844

This finishes implementing fullscreen support.

https://bugzilla.gnome.org/show_bug.cgi?id=769329

This will be used in the next commit to implement fullscreen support.

https://bugzilla.gnome.org/show_bug.cgi?id=769329

Make ApplicationWindow handle the UI state of the content box and use
CollectionBox and DisplayBox that have been extracted from ContentBox in
the previous commits.

This better distributes the concerns of the different parts of the UI.

Fixes #312

Make ApplicationWindow handle the UI state of the header bar and use
CollectionHeaderBar and DisplayHeaderBar that have been extracted from
HeaderBar in the previous commits.

This better distributes the concerns of the different parts of the UI.

Ensures we paused and tried to save the game before checking if we can
safely quit it.

This avoids quitting a game which can quit safely before it saved.

Fixes #288