Flat mouse accel is fairly obvious.
Hi-Res scrolling is an option that is useful on certain mice that technically support 'pixel-perfect' scrolling, but still 'click' like regular mice would when you scroll. Some mice are designed to use pixel-perfect scrolling, so keeping it optional is useful.
pavucontrol does the same thing e and emixer do - monitor
input/recording sources to show a vu meter to show current input
levels when appropriate. ignore these as they are not actually
recording audio - just monitoring them and thus from a user experience
point of view probably should be ignored.
Why this? A way to have a shared store of "variables" or states that
any part of e or modules can store some simple things in and thus also
broadcast changes to state, listen to changes in state and react.
I am thinking of things like advertising:
"/power/ac" = [ true | false ]
"/power/battery/low" = [ true | false ]
"/power/battery/charging" = [ true | false ]
"/power/state" = [ "on" | "sleep" ]
"/screen" = [ "on" | "dim" | "blank" ]
"/screen/locked" = [ true | false ]
"/network/online" = [ true | false ]
"/network/location" = "name of network detected"
so some apps/clients mess with screensaver/blanking/dpms behind e's
back. work around this - every 10 sec poll and check (ugly) and if
things are nto set as they should be ... force them to be set that
way. may lead to fights over this but too many people complaining
about steam or other apps messing with this.
You know...If we actually enforced our code formatting rules before
commit, then I could be saving a lot of time by not having to make a
bunch of formatting commits just so code is readable :/
NB: No functional changes
Something has changed in x where now rotated displays if you have
multiple screens don't vcome up right - an alternate for now is to run
xrandr commandline if it exsts. Not stricly a fix - a workaround.
wl does not have fallback rendering, therefore we always fallback to
default. In x11 we fallback to x11 rendering the cursor.
This should logically now not result in the cursor canvas beeing
deleted.
Make this dialog resizable for reading longer text (window titles,
etc). Also, fix the layout silliness that was going on by aligning the
table entries properly.
This dialog looked like crap :( Let's fix that :)
For some reason I have yet to divine we don't get an initial unmap
event due to the reparent of the energyxt dialog windows and the
"ignore that first unmap" flag does not get cleared because it doesn't
happen. later when the dialog is withdrawn {9unmapped) this is ignored
then when you close the dialog... thus keeping it around as far as e
is concerned.
so to fix this - add a small timeout to clean this flag after a
show/map.
@fix
we didn't support enough of noktifications to make everyone happy -
this is why ffox, chrome etc. did their own notification windows and
didn't use e's notifications. we now advertise doing everything. we
say w edo sound though don't.... will add that later, but this now
means we really do a lot more and thus pushes these other
notifications into e's notifications so we're much better now and this
annoyance i have noticed is now gone.
@feat
right clikc -> actions -> ... here
you might want desktop files that have
X-Enlightenment-Action-Mime=inode/directory
in them - then they will be included in that menu and whatever is
executed is passed the dir when run as an argument. example:
[Desktop Entry]
Type=Application
Name=Dir xmessage
Exec=xmessage
Icon=video_player
NoDisplay=true
X-Enlightenment-Action-Mime=inode/directory
assume it went to 0 size if removed and already a csd frame window
which is what chomium does going fullscreen - i didnt see this as i
used chromium with system titlebars not its own.
@fix
shaped input doesnt affect or make custom copies of pixel data, thus
precise inside can't work (it can only work if the pixel data is local
- thus textur efrom pixmap is not going to produce valid data thus...
you get the drift). this fixes some odd focus/event things with some
windows that use shaped input only
@fix
this will clearly alert a user they are using e in wayland mode. this
is needed as there seems to be far too much confusion if e is in
wayland or not and when it is people having issues. this makes sure
e's wayland session desktop also has the label in it so it's clear etc.
also getrlimit to know if we can lower nice level, you will want
something like:
* - nice 0
in /etc/security/limits.conf to allow for users to both raise and
lower nice level up until this limit (ie not negative nice levels).
perhaps enlightenment_system needs to do this...
just because an item is not the selected one does not mean it should
be disabled. that is not how radios work. you choose 1 of n menu
items... only items you should NOT select (are not available for
selection) should be disabled.
@fix
Add an event handler for E_CLIENT_FULLSCREEN. Remove the client,
destroying the popup and icon region.
This resolves the issue where a client fullscreen request would
leave a rogue icon region and popup if switching to full screen
with some applications.
@fix T8996
it's not right that windows stay shaded, iconified or stacked below
when you use a binding to switch focus like "focus prev" to cycle just
with a plain key. this fixes that
@fix
we get a spurious mouse out if your window is small then told to go
fullscreen which then causes in ponter focus a unfocus event which
causes e to restore window to its non-fulscreen mode which then may
cause a mouse in again if mouse is positioned right which causes a "go
fullscreen now again" and so on... fix this and ignore that mouse out
right after going fullscreen.
@fix
Carsten Haitzler
Ross Vandegrift
Nekobit
kikadf
Christopher Michael
maxerba
Marcel Hollerbach
Simon Tischer
l05o
Alastair Poole