[e-users] Re: On Top Modules

[Martin G. <mge...@mg...>]

Fabian Zeindl <fa...@xo...> writes:

> Paul S. wrote:
>> Nope, that's an e18 feature.
>
> Can you tell me why? I know there are things like feature freeze
> etc., but I think that would bring much benefit (e.g. engage would
> be far more usable).

I'm not one of the developers, but let me try and answer anyway...

I believe that the problem is that engage and the other modules use
transparency in huge amounts.  Right now this transparency is made
against the root window, and everything is easily controlled by E17
since it has control over the root window.

If engage were to be ontop, then the transparency would have be do
done against other windows not controlled by E (Firefox, Eterm, and
whatnot...), not just the root window.

And for that I think we're waiting for the next version of X to
support true transparency between arbitrary windows.

What could be done now is to have engage and the other modules reserve
some space so that windows wont be allowed to be moved into those
areas.

In fact, there's already some support for this in the mazimization
policies: with the SMART, EXPAND, and FILL policies your maximized
windows wont cover the modules.  Use

  enlightenment_remote -maximize-policy-set SMART

to change policy.

=2D-=20
Martin Geisler                                     GnuPG Key: 0x7E45DD38

PHP Exif Library      |  PHP Weather             |  PHP Shell
http://pel.sf.net/    |  http://phpweather.net/  |  http://mgeisler.net/
Read/write Exif data  |  Show current weather    |  A shell in a browser