summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarsten Haitzler (Rasterman) <raster@rasterman.com>2016-11-16 11:25:11 +0900
committerCarsten Haitzler (Rasterman) <raster@rasterman.com>2016-11-16 11:25:11 +0900
commitc3ec526cec23c6bf571d388841a8f59bdfb8661c (patch)
treee9696537848161c69dd1acb983f0a3d1e9688de9
parent573035e262d3d69b7e8116969deaf85a7718ef89 (diff)
downloadenlightenment-c3ec526cec23c6bf571d388841a8f59bdfb8661c.tar.gz
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 b56d07a25a..37a1089246 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)
wiz_module = m;
e_wizard_init();
- e_config->scale.use_dpi = 0;
- e_config->scale.use_custom = 1;
- e_config->scale.factor = 1.2;
- e_scale_update();
src_path = getenv("E_MODULE_SRC_PATH");
if (src_path)
snprintf(buf, sizeof(buf), "%s/.libs", e_module_dir_get(m));