Re: [Chromium-dev] render_to_app_window

[Mike H. <mho...@gr...>]

In the case of crdemo.conf, you'll want to remove all the "server" code 
and change the "client" to use the renderspu.  Set the client's render 
spu to 'render_to_app_window'.  In this case, you should only have to 
run 'crappfaker' and not 'crserver'.

There is no meaning for the server to render to the application's window 
in it's current semantics.

-Mike

Dale Beermann wrote:
> Hi everyone,
> 
> My name is Dale Beermann and I'm going to be Greg's student working on the
> CRUT stuff. I'm currently in the process of learning Chromium and starting
> work on CRUT.  While I'm in the learning stages, I may need to ask for
> help or explanation from some of you from time to time.  I'm wondering if
> someone can explain an error that I'm receiving.
> 
> I was having problems getting crappfaker to work correctly, it was using
> the system's libGL.so rather than having Chromium intercept it.  I looked
> through the old email archives and got it to work correctly by setting
> LD_PRELOAD.  I am just using crdemo.conf and atlantis.  My first step
> towards working on CRUT was going to be to get render_to_app_window to
> work.  Once I finally got Chomium to work correctly, I tried adding the
> line 'server_spu.Conf( 'render_to_app_window', 1)' and received an error
> on the server I can't undertand yet, here's a partial output:
> 
> CR Debug(localhost:1746): Connecting to server localhost on port 10000,
> with protocol tcpip
> CR Debug(localhost:1746): Done connecting to server.
> CR Debug(localhost:1746): Accepted connection from "localhost".
> CR Debug(localhost:1746): No tiling information for server!
> CR Warning(localhost:1746): Total output dimensions = (0, 0)
> CR Debug(localhost:1746): Adding to the run queue: client=0x8166598
> number=0 count=1
> CR Debug(localhost:1746): CALLING INIT ON 0x80e7060
> CR Debug(localhost:1746): Buffer pool was empty, so I allocated 32788
> bytes
> CR Debug(localhost:1746): Render SPU: Looks like we have GLX
> CR Debug(localhost:1746): Render SPU: Chose visual id=0x24: RGBA=(8,8,8,0)
> Z=16 stencil=8 double=1 stereo=0 accum=(16,16,16,0)
> CR Debug(localhost:1746): Render SPU: Created the window on display :0.0
> CR Debug(localhost:1746): Render SPU: About to make current to the context
> CR Debug(localhost:1746): Render SPU: actual window x, y, width, height:
> 100, 100, 500, 500
> CR Debug(localhost:1746): Render SPU: Created a context (indirect)
> CR Debug(localhost:1746): Creating a context (id=0 addr=0x8181308)
> X Error of failed request:  BadMatch (invalid parameter attributes)
>   Major opcode of failed request:  143 (GLX)
>   Minor opcode of failed request:  5 (X_GLXMakeCurrent)
>   Serial number of failed request:  25
>   Current serial number in output stream:  25
> 
> 
> I apologize for my ignorance here, I'm trying to learn Chromium as fast as
> possible.  I'm wondering if anyone has done any work with this and would
> be able to explain what's going on.  I appreciate any help possible.
> Thanks and I'll look forward to working with you all in the future.
> 
> Dale
> 
> 
> 
> -------------------------------------------------------
> This sf.net emial is sponsored by: Influence the future 
> of  Java(TM) technology. Join the Java Community 
> Process(SM) (JCP(SM)) program now. 
> http://ad.doubleclick.net/clk;4699841;7576298;k?http://www.sun.com/javavote
> _______________________________________________
> Chromium-dev mailing list
> Chr...@li...
> https://lists.sourceforge.net/lists/listinfo/chromium-dev