[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [E-devel] E CVS: apps/e sebastid
On Mon, 17 Jul 2006 17:03:55 +0300 "Hisham Mardam Bey"
> On 7/17/06, Enlightenment CVS <firstname.lastname@example.org> wrote:
> > Enlightenment CVS committal
> > Author : sebastid
> > Project : e17
> > Module : apps/e
> > Dir : e17/apps/e/src/bin
> > Modified Files:
> > e_border.c e_border.h
> > Log Message:
> > Correct fix for fullscreen border.
> > On fullscreen set window size to fullscreen and trigger border change. The
> > border change will remove the border on fullscreen and reset to the correct
> > border on unfullscreen, whilst keeping the correct border size and border
> > inset.
> > A similar change should also be done for maximized borders.
> Is it E or the app's problem when we go out of fullscreen? If you try
> xine or mplayer, going out of fullscreen using the 'f' key will move
> the app to pixel [0,0] in the case of mplayer, and [0,0] on the
> corresponding head in the case of xine. This is using twinview.
depends on the app and the version - some apps "diy" fullscreen which simply
means override-redirect window, raised and placed to cover all of the root
window. some apps send a netwm message asking for fullscreen (then its e's
problem to do it) and some do a half-way house where they change properties and
maybe hide and remap a window to ask for it to be borderless (eg xmms does this
normally) and then ask for its position/size and layering to be such that it
fills the screen. so really - there are 3 possible ways you will see this
happen. it will take some debugging to find out which one it is per app.
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) email@example.com
Tokyo, Japan (東京 日本)