#include "gui/screen_metrics.h"
#include "widgets/widget_settings.h"

Include dependency graph for screen_metrics.c:

Functions
double	dt_screen_dpi (void)

void	dt_screen_set_dpi (double dpi)

double	dt_screen_dpi_factor (void)

void	dt_screen_set_dpi_factor (double factor)

double	dt_screen_ppd (void)

void	dt_screen_set_ppd (double ppd)

gboolean	dt_screen_metrics_probed (void)

double	dt_screen_em_size (void)

void	dt_screen_set_em_size (double em)

Function Documentation

◆ dt_screen_dpi()

double dt_screen_dpi ( void )

Screen resolution in dots per inch. Defaults to 96.0 (the X/GDK default).

Definition at line 31 of file screen_metrics.c.

References dt_widget_dpi().

◆ dt_screen_dpi_factor()

double dt_screen_dpi_factor ( void )

dpi / 96, i.e. how much to scale UI lengths by. Defaults to 1.0.

Definition at line 34 of file screen_metrics.c.

References dt_widget_dpi_factor().

◆ dt_screen_em_size()

double dt_screen_em_size ( void )

Height of the theme font's "em", in pixels. Defaults to 16.0.

Definition at line 42 of file screen_metrics.c.

References dt_widget_em_size().

◆ dt_screen_metrics_probed()

gboolean dt_screen_metrics_probed ( void )

TRUE once something has actually interrogated a display and pushed real values.

The getters above are always safe to call, but they answer with neutral defaults until this returns TRUE. Use it where reporting an invented 96dpi/1.0 would be worse than reporting nothing – a crash report or a telemetry payload – and NOT as a "is there a GUI?" test for scaling, where the neutral defaults are exactly the right answer.

Definition at line 40 of file screen_metrics.c.

References dt_widget_metrics_probed().