mirror of
https://github.com/JetSetIlly/Gopher2600.git
synced 2025-04-02 11:02:17 -04:00
d32262adff
debugger no longer sends play, pause notifications to the gui. the gui polls for that information as required govern package now has SubState type to complement the State type. StateIntegrity() function enforces combinations of State and SubState, called from debugger.setState() function playmode notifications reworked and contained in a single playmode_overlay.go file. this includes the FPS and screen detail preference value sdlimgui.playmode.fpsOverlay replaced with sdlimgui.playmode.fpsDetail. still toggled with F7 key coproc icon moved to top-left corner of playmode overlay and only visible when FPS detail is showing when FPS detail is showing multiple (small) icons care shown. when it is not showing, a single (large) icon is shown according to the priority of the icon. eg. pause indicator has higher priority than the mute indicator
36 lines
1.7 KiB
Go
36 lines
1.7 KiB
Go
// This file is part of Gopher2600.
|
|
//
|
|
// Gopher2600 is free software: you can redistribute it and/or modify
|
|
// it under the terms of the GNU General Public License as published by
|
|
// the Free Software Foundation, either version 3 of the License, or
|
|
// (at your option) any later version.
|
|
//
|
|
// Gopher2600 is distributed in the hope that it will be useful,
|
|
// but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
// GNU General Public License for more details.
|
|
//
|
|
// You should have received a copy of the GNU General Public License
|
|
// along with Gopher2600. If not, see <https://www.gnu.org/licenses/>.
|
|
|
|
// Package notifications allow communication from a cartridge directly to the
|
|
// emulation instance. This is useful, for example, by the Supercharger
|
|
// emulation to indicate the start/stop of the Supercharger tape.
|
|
//
|
|
// Notifications are sometimes passed onto the GUI to inidicate to the user the
|
|
// event that has happened (eg. tape stopped, etc.) For some notifications
|
|
// however, it is appropriate for the emulation instance to deal with the
|
|
// notification invisibly.
|
|
//
|
|
// Finally, some notifications are not generated by the cartridge but by the
|
|
// emulation instance, and sent to the GUI.
|
|
//
|
|
// We can therefore think of the flow of notifications in the following manner:
|
|
//
|
|
// (a) (b) (c)
|
|
// Cartridge -----> Emulation Instance -----> GUI ----
|
|
// 1 2 \____| 3
|
|
//
|
|
// The diagram also suggests that a GUI can both produce and receive a
|
|
// notification. This is possible and sometimes convenient to do.
|
|
package notifications
|