<br><br><div class="gmail_quote">On Mon, Apr 7, 2008 at 10:36 AM, andrew rader <<a href="mailto:andrew.r.rader@gmail.com" target="_blank">andrew.r.rader@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi all,<br> <br> I've recently become interesting in how all of the pieces of X/compiz<br> come together to do what it does, and after going through compiz's<br> code, I have a few questions that I just can't seem to find any<br> answers to.<br> </blockquote><div> <br><snip></div><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">first, how does compiz know what geometry to use for the textured<br> "window" objects? It obviously can't use the width and height of the<br> window, since opengl's coordinates are going to be much different (ie.<br> between -1 and 1). I tried looking through the code, but I can't find<br> anything that appears to convert from X window coords to OpenGL<br> coords.<br> <br> second, how is the user's input mapped to windows? If my understanding<br> of compiz being an opengl app is correct, any input will be to the<br> compiz window rather than the window the user perceives to be active.<br> Is there a simple way of redirecting these inputs? or does compiz have<br> to manually map an input event to the correct window?<br> </blockquote><div><br>Just catching up on this list, and am curious about the same questions.  <br><br>I don't see a response on the list, did you get a private response you can<br>share with the list, or does someone have links to where to read more about<br> this?<br><br>Shane...<br></div></div>