scale - dont use nan as unsed but < 0.0 because this messes up
i found that the isnan messes up... and even tho it's nan it says its not thus forcing tmp to be on all the time. using < 0 will be more reliable for sure as scaling valuses <= 0 are just "invalid" anyway.
This commit is contained in:
parent
1a7df68b84
commit
da88dd1128
|
@ -803,7 +803,7 @@ elm_main(int argc, char **argv)
|
|||
Eina_Bool single = EINA_FALSE;
|
||||
Eina_Bool no_wizard = EINA_FALSE;
|
||||
Eina_Bool cmd_options = EINA_FALSE;
|
||||
double scale = NAN; /* unset */
|
||||
double scale = -1.0; /* unset */
|
||||
Ipc_Instance instance = {
|
||||
.login_shell = 0xff, /* unset */
|
||||
.active_links = 0xff, /* unset */
|
||||
|
@ -915,7 +915,7 @@ elm_main(int argc, char **argv)
|
|||
goto end;
|
||||
}
|
||||
|
||||
if (!isnan(scale))
|
||||
if (scale > 0.0)
|
||||
{
|
||||
elm_config_scale_set(scale);
|
||||
elm_config_all_flush();
|
||||
|
|
Loading…
Reference in New Issue