Vincent Torri wrote: --snip--
>> WTH !!! >> >> Who broke ecore_x ?? > > me > >> This also effects ecore_x_default_screen_get. >> These functions are not specific to ecore_xcb, but rather are generic >> ecore_x functions, so this needs to be fixed like NOW !!!!!!!! > > that kind of functions are used only for xcb Really? then why have a ecore_x convenience function for getting the current display ? IMO, this is a nice function to have for people that don't know much about X programming, but wanna make use of ecore_x. (well, for > ecore_x_default_screen, i can add it for Xlib too, even if it is really > needed for XCB as it is not stored at all, contrary to Xlib which stores > the default screen in the Display structure), Regardless if Xlib stores it or not, the point of having something like ecore_x is to make it easy for people to code apps using X. as mentioned in the > documentation. So, except me (I don't think that someone else is using > ecore with xcb), nobody should use those files. > > I *know* that i need to add them for the Xlib backend. > --snip-- > > Vincent > dh ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
