- Documentation of containers, core, and format
This commit is contained in:
@@ -51,9 +51,9 @@ class display_server;
|
||||
///
|
||||
/// \details An implementation for a display server should inherit `display_server_base` and note the following:
|
||||
///
|
||||
/// For a server type `DisplayT`; any `gfxcontext` implementation that wishes to implement `DisplayT`
|
||||
/// For a server type \f$DisplayT\f$; any \f$gfxcontext\f$ implementation that wishes to implement \f$DisplayT\f$
|
||||
/// must provide a constructor that accepts a `DisplayT*`. `DisplayT::ctx_registry::register_type` must then be
|
||||
/// called for the `gfxcontext` implementation.
|
||||
/// called for the \f$gfxcontext\f$ implementation.
|
||||
class display_server : public type_registry<display_server, platform*> {
|
||||
// Typedefs/Constants/Enums ============================================================================================
|
||||
public:
|
||||
@@ -134,6 +134,8 @@ protected:
|
||||
}
|
||||
};
|
||||
|
||||
///
|
||||
/// \brief Interface resembling the API for a display server of an operating system, e.g. Linux X11/Wayland
|
||||
template<typename DisplayT, typename WindowT>
|
||||
class display_server_base : public display_server, public type_registry<gfxcontext, DisplayT*> {
|
||||
public:
|
||||
|
||||
Reference in New Issue
Block a user