Scenic.ViewPort.Driver behaviour (Scenic v0.10.3) View Source

Drivers make up the bottom layer of the Scenic architectural stack. They draw everything on the screen and originate the raw user input. In general, different hardware platforms will need different drivers.

Drivers deal with graphs and do not know anything about scenes. This means that they are pretty generic. Drivers don't really understand that a component is a separate thing either, other than the fact that it has a graph that needs to be drawn.

Link to this section Summary

Functions

child_spec(init_arg)

Returns a specification to start this module under a supervisor.

init(arg)

Callback implementation for GenServer.init/1.

start(viewport, config)

start_link(args)

stop(driver_pid)

Callbacks

handle_call(any, any, any)

handle_cast(any, any)

handle_info(any, any)

init(viewport, size, config)

Link to this section Functions

child_spec(init_arg)

Returns a specification to start this module under a supervisor.

See Supervisor.

init(arg)

Callback implementation for GenServer.init/1.

start(viewport, config)

start_link(args)

stop(driver_pid)

Link to this section Callbacks

handle_call(any, any, any)

Specs

handle_call(any(), any(), any()) :: {:reply, any(), any()} | {:noreply, any()}

handle_cast(any, any)

Specs

handle_cast(any(), any()) :: {:noreply, any()}

handle_info(any, any)

Specs

handle_info(any(), any()) :: {:noreply, any()}

init(viewport, size, config)

Specs

init(
  viewport :: GenServer.server(),
  size :: Scenic.Math.point(),
  config :: any()
) :: {:ok, any()}