summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarsten Haitzler (Rasterman) <raster@rasterman.com>2016-11-16 11:25:11 +0900
committerMike Blumenkrantz <zmike@osg.samsung.com>2016-11-18 11:46:23 -0500
commit117e30310d50fb068b6fb53558f7b02ab21167e8 (patch)
treeec09a7e4eafc5dc4b63db1b95f1bdb0a6ea8cdb8
parentc4339eb273eb9072294811889d78dbc3c7b413e7 (diff)
wizard - do not set scale to 1.2 forcibly. use dpi as the def prof says
the default profiel is configureed to use dpi to scale. if dpi goes up so does wizard scaling. setitng to 1.2 forcibly is just wrong. imagine a uhd screen thats 13" or imagine an 8k display... at least if dpi can be read correctly things work out find. think the base dpi of 90 is too high - then adjust that in profile... but not in wizard code. this has been here a while and i always thought this scaling bumping was a dpi effect. it wasnt. it was hardcoded. bad bad. @fix.
-rw-r--r--src/modules/wizard/e_mod_main.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/modules/wizard/e_mod_main.c b/src/modules/wizard/e_mod_main.c
index b56d07a25..37a108924 100644
--- a/src/modules/wizard/e_mod_main.c
+++ b/src/modules/wizard/e_mod_main.c
@@ -53,10 +53,6 @@ e_modapi_init(E_Module *m)
53 wiz_module = m; 53 wiz_module = m;
54 e_wizard_init(); 54 e_wizard_init();
55 55
56 e_config->scale.use_dpi = 0;
57 e_config->scale.use_custom = 1;
58 e_config->scale.factor = 1.2;
59 e_scale_update();
60 src_path = getenv("E_MODULE_SRC_PATH"); 56 src_path = getenv("E_MODULE_SRC_PATH");
61 if (src_path) 57 if (src_path)
62 snprintf(buf, sizeof(buf), "%s/.libs", e_module_dir_get(m)); 58 snprintf(buf, sizeof(buf), "%s/.libs", e_module_dir_get(m));