so a whole back terminology moved from the shipepd nexus bitmap font
to system monospace fonts and 12 pt. it has always looked wrong as
efl's default theme is 10 and relies on a system-wide scale factor to
do this. 12 has looked totally out of place for a long time and it's
time that this not be hacked around in terminology but be solved at
the system level - maybe efl. if you use e then you will have selected
the scaling factor already and it will affect efl apps and all work.
outside of e is "not solved". to date it's been "other desktosp have
to support efl - up to them". perhaps looking at some level of "well
user has no config so let's guess what scale factor should maybe be
based on dpy and other toolkit configs we can find etc." in EFL... not
terminology.
This reverts commit 5c0167c5e1.
Porkepix on IRC pointed this out and it actually does the reverse of make
blue more readable. compare:
before:
https://framapic.org/EvV0cVyAUKUm/OZIdkLB4pOCn.png
after:
https://framapic.org/hX2gczT1jGMU/jtu3mJ3eQE2E.png
notice the bg of the bar at the bottom now become a lighter blue
making numbers hard to read. the darker blue was chosen because that
is actually the blue color used in xterm and the linux console (or
closer to it with a bit of a muted coloring to it rather than totally
pure). :( so sorry - this IMHO goes backwards and Porkepix did point
it out too.
donecb must be called after the settings objects have been deleted.
Otherwise focus manager will detect that a focused object is deleted,
and performe recoverty things. Those recovery things end up in
terminology in focusing nothing, since the terminal object is not a
elementary widget. Not beeing a elementery widget here means that it is
not visible from the POV of the focus manager.
However, when we emit donecb later on, then the focus is restored (in
the callback) after focus manager has performed its voodoo.
This fixes focus disappearing after going into the settings and going
out of them again.
Reviewed-by: Boris Faure <billiob@gmail.com>
Differential Revision: https://phab.enlightenment.org/D8932
donecb must be called after the settings objects have been deleted.
Otherwise focus manager will detect that a focused object is deleted,
and performe recoverty things. Those recovery things end up in
terminology in focusing nothing, since the terminal object is not a
elementary widget. Not beeing a elementery widget here means that it is
not visible from the POV of the focus manager.
However, when we emit donecb later on, then the focus is restored (in
the callback) after focus manager has performed its voodoo.
This fixes focus disappearing after going into the settings and going
out of them again.
Reviewed-by: Boris Faure <billiob@gmail.com>
Differential Revision: https://phab.enlightenment.org/D8932