On Tue, 13 Oct 2015 16:43:56 -0700 Cedric BAIL <moa.blueb...@gmail.com> said:
> On Tue, Oct 13, 2015 at 9:12 AM, Cedric BAIL <moa.blueb...@gmail.com> wrote: > > Le 13 oct. 2015 03:44, "Carsten Haitzler" <ras...@rasterman.com> a écrit : > >> raster pushed a commit to branch master. > >> > >> http://git.enlightenment.org/core/efl.git/commit/?id=23f5a5092cdb8fff0efada89dfeadf1deceef3b9 > >> > >> commit 23f5a5092cdb8fff0efada89dfeadf1deceef3b9 > >> Author: Carsten Haitzler (Rasterman) <ras...@rasterman.com> > >> Date: Tue Oct 13 19:43:18 2015 +0900 > >> > >> Revert "Revert "Revert "evas: fix borked rotation support in GL > >> engine.""" > >> > >> This reverts commit f51168f4ec7a1bd3072428c7a271ad7c6715fde5. > >> > >> if this is right or not... this RESULTS in enlightenment becoming > >> totally unusable. put this back WHEN other issues are fixed you think > >> that exist. last i knew we query yinvert start with glx per native > >> surface and use that info - so as best i know it is and has been right > >> for a long time. > > > > Well before my patch, yinvert was completely ignored. We didn't get the > > right value from the driver and the code that was doing the yinvert would > > never have been taken. I don't have a driver that expose a yinvert surface, > > so I can only test the disabled case, and that one work for sure. Can you > > check if your driver does support yinvert. If it does, you will have to look > > why it display things still in an inverted way. Maybe we are not saying we > > handle yinverted surface. I don't know,I can't test. > > Actually your revert does create a problem for some user of Intel who > do now see an inverted world. I don't see it and I have the same > driver as the guy who reported the problem. I have found back then the > following discussion: > https://bugs.freedesktop.org/show_bug.cgi?id=78966 and I am wondering > if we haven't just disabled our Yinvert support for a year in fact. > Can you investigate what your driver say and why things are up side > down ? I am close to think we should just drop all the Yinvert > support. i will check - but i know i actually added yinvert checking code YEARS ago. it's been there for a long time. you changes cause my entire display to have every window yinverted which basically makes it impossible to debug and fix. :) as this is a pretty severe change and it's not just on both my desktops (nvidia drivers), users on #e started reporting it too yesterday so we went from almost no issues to suddenly a bunch of systems affected. it's not a minor issue so this kind of has "stay as is" until something better is done. :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
