9200094203
This has multiple effects: 1) The i3 codebase is now consistently formatted. clang-format uncovered plenty of places where inconsistent code made it into our code base. 2) When writing code, you don’t need to think or worry about our coding style. Write it in yours, then run clang-format-3.5 3) When submitting patches, we don’t need to argue about coding style. The basic idea is that we don’t want to care about _how_ we write the code, but _what_ it does :). The coding style that we use is defined in the .clang-format config file and is based on the google style, but adapted in such a way that the number of modifications to the i3 code base is minimal.
17 lines
522 B
C
17 lines
522 B
C
#include "libi3.h"
|
|
#include <math.h>
|
|
|
|
extern xcb_screen_t *root_screen;
|
|
|
|
/*
|
|
* Convert a logical amount of pixels (e.g. 2 pixels on a “standard” 96 DPI
|
|
* screen) to a corresponding amount of physical pixels on a standard or retina
|
|
* screen, e.g. 5 pixels on a 227 DPI MacBook Pro 13" Retina screen.
|
|
*
|
|
*/
|
|
int logical_px(const int logical) {
|
|
const int dpi = (double)root_screen->height_in_pixels * 25.4 /
|
|
(double)root_screen->height_in_millimeters;
|
|
return ceil((dpi / 96.0) * logical);
|
|
}
|