forked from enlightenment/enlightenment
so e has a bit of a problem. we mostly deal with zones, BUt these zones come from our old xinerama code (this likely should just die some time) and THIS code gets fed info from e's randr code. we re-fill/modify as randr finds new screens or things get reconfigured. thus zones adapt. the problem is now all our zone code really has a hard time reverse mapping the zone back to where it came from -eg the randr screen data. you literally can't do a whole bunch of things like know if that zone was an internal laptop lid or an external screen, or if it was rotated or even what the dpi is... as you ave no deasy way to map it back other than by guessing geometry matches. this fixes that by storing the randr screen id (which should be unique) fromt he original src randr screen in the xinerama screen and then in the zone. with this you can do a quick lookup in the e randr data should you ever need to find the info. this should pave the way for some other fixes/improvements, but without this they cannot be done. @fix |
||
---|---|---|
config | ||
data | ||
doc | ||
m4 | ||
pkgbuild | ||
po | ||
src | ||
.arcconfig | ||
.gitignore | ||
.mailmap | ||
AUTHORS | ||
BUGS | ||
COPYING | ||
ChangeLog | ||
INSTALL | ||
Makefile.am | ||
NEWS | ||
README | ||
README.wayland | ||
autogen.sh | ||
configure.ac | ||
e19_workdir_setup.sh | ||
enlightenment.pc.in | ||
enlightenment.spec.in | ||
netwm.txt | ||
x-ui.sh | ||
xdebug.sh |
README
Please report bugs and send patches to phab.enlightenment.org Enlightenment 0.19.0 Requirements: ------------- Must: efl elementary libc libm libX11 libXext xcb xcb-shape xcb-keysyms Heavily suggested: evas_generic_loaders (all loaders) NOTE: Users of DR16 will need to rename the $prefix/bin/enlightenment file prior to installing DR19 or it will be overwritten. You can also use the configure --prefix option to put enlightenment in a separate tree of its own (recommended) like: ./configure --prefix=/usr/local/e19 You will, as usual, need to add the subsequent bin dir to your $PATH etc. NOTES: * if you do not want security issues make sure sysactions.conf is in /etc/enlightenment (not PREFIX/etc/enlightenment) as this is the first place it looks at. This file is intended to be customized by packagers and system integrators to match your policies and scripts/tools.