Summary: On high resolution displays, "everything" was too small. so increase the values to make it bigger if needed
Reviewers: devilhorns, raster
Reviewed By: raster
Subscribers: cedric, zmike
Tags: #e_modules
Differential Revision: https://phab.enlightenment.org/D12193
As this was reported with no reproduction method - like a "one off" I
can't be sure this is it and fixes it, but looking for agent->msg and
it becoming a wild crazy pointer. So either it was left there from
long ago and has since been forgotten bhy asan and is thus wild, or ..
memory was scribbled over with junk. in the latter case... who knows.
in the former, this may fix that.
@fix
on other screens the menus were ... wrong - coords were not right
(previous commit)b ut then scroll-to-fix also moved them badly. this
is now fixed too.
@fix
now have a base dpi (75) which is multiplied by the scale factor and
then set in both xft.dpi and xsettings. also a checkbox to turn
setting of this on or off so e can be told to not touch these at all.
initial "how do i size and lay this out" is a fuzzy algo that tries to
stuff all the windows into a single screen with several rows of
windows (in large mode). it has to trade off sizing for a squarish
layout with mu;ltiple rows so does some passes and tries and bisecting
etc. - the problem is each stage goes and does a lot of object changes
re-laying them out and querying them. this is expensive. this does a
row length calc on its own without the objects to save a whole lot of
overhead.
in theory i could actually skip almost all the object stuf and make
more assumptions and reduce the object fiddliong to just an initial
"how much fluff around a window item in the list and how much fluff
around the winlist (like padding/title and so on) and then just do
some raw math (and even flatten into arrays for cache friendliness).
but it's fast enough right now without a lot of changes. can always
revisit this in future.
otherwise we just get warnings all day. this is a bug and efl
plastered over it and didnt die by being nice - but we shiouldnt keep
the bad code...
@fix
this mens fwin's key handling should always be called after efm's own
internal handling and dispatching. also the final deletion will also
now be deferred in a job to "after all of this".
fix segv on ctrl+w
if the list of device names is the same with a devices update event
then assume its the same as before and dont go probing all their
properties which takes time and round-trips which is not good.
1. use max valu in the get and store it once a get has been done so it
will get backlight level right on unsuaul monitors that do not use
0->100
2. detect as an error dinfing 2 screesn with the same edid and log it
3. use ddca_enable_sleep_suppression() to try speed up things a bit to
sleep less inside ddcutil
found hot spot was not being tracked right as callbacks for obj moves
arent in sync with getting part geom - so get geom of the swallowed
obj itself. then hot geom is right and the hot limitign ensures a bad
theme design with out of bound hot geom wont lead to bland cursors
@fix
this uses new efl functions so ... you need a git efl now (and
eventually 1.26). this sets Xft.dpi to match the xsettings dpi etc.
etc. ... so it all matches up.
if e' x applications setitnghs (xsettingvs) is off - then just
calculate an xsettings dpi val from core scale. also use randr info
for dpi if possible instead of "core x" and "core wl". wprkds around
broken core dpi in x.
Carsten Haitzler
maxerba
Alastair Poole