From: <ma...@co...> - 2005-06-09 00:55:20
|
Mike, Thanks for the suggestion, but I think that concept has led to the Windows render-to-app-window problem in the first place... I think the problem is that one processes can't render into another's Window (window id's might be process- specific ) I don't know for sure what the cause is, but the existing implementation definitely doesn't work! In the meantime, I went ahead with my plan and it looks like it works! (For single window apps anyway... and so far I've only tried city...) Having the stub itself double dispatch to the spus and the app window should be higer performance anyway, since you're not sending the calls off to another process, right? The only tricky part is handling which context is the current native context, but another half day and a hash table or two should settle that... Thanks, Jon ps. The IEEE Vis talk that you, Brian, et. al. put on has been super valuable. Thanks again for having done that! Will there be another this year? Jonathan Marbach BP Center for Visualization University of Colorado Quoting Mike Houston <mho...@gr...>: > The main issue on the windows side is someone figuring out how to pass > the gid(?) information around so Chromium can grab the window. Under > *nix, this is pretty easy through X11. I would suggest following along > the X11 path and see if something similar can be done on the Windows path. > > -Mike > |