when u switch songs with popup the album art flickered on/off a few
times because mnpris props updated multilpe times. this ignores new
art url changes if they are the same file/url to avoid flickers.
now music-control can automatically find any mpris provider if its in
a glob domain like org.mpris.MediaPlayer2.* or web browsers like
org.mpris.MediaPlayer2.chromium.* and org.mpris.MediaPlayer2.firefox.*
... as well as the explicit list it has still. if it doesnt have a
provider it polls every 5 sec to look for one.
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
Carsten Haitzler
maxerba
Alastair Poole