On Thursday 11 May 2006 07:22, muzzle wrote: mu: > mu: > it's not impossible - it's explicitly not allowed in code: mu: > mu: > if (!border->is_maximized) shade_window(); mu: > mu: > it literally has extra checks to stop the shading if its maximized. mu: mu: mhm, that's what I was thinking too, "impossible" as "not allowed in code". mu: Would you consider making it configurable (ie let a theme specify if mu: maximized windows can be shaded or not)? mu: mu: I thought enlightenment was all about customization, or are there any mu: other reasons to avoid it? mu: mu: Bye, mu: mu: Emme
That is the beauty of OSS. If you want it configurable, adding an or to the test condition wouldn't be too hard. You could even send a patch upstream and request it's inclusion. Even if you aren't into coding, finding the test condition and changing the condition to TRUE. I really would expect people using software as highly alpha/beta as e17 to at least be able to stumble through the code. You said "are there any other reasons to avoid it?" Not to sound [insert a descriptive word here], I am not exactly "active" with e17's development myself, but if you aren't capable of doing the changes and recompiling, you may look at e16 or another wm until e17 starts to go final. I fully believe e17 will be a beautiful thing once development has stabalized. DaeGlo ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
