Re: [GtkGLExt] Creating a new widget type vs. modifying an instance of an existing type

[Alif Wahid <alif wahid gmail com>]

Hi Braden,

> For various reasons I thought it better to change this approach to one
> where I simply use GtkDrawingArea directly and add GL capabilities and
> event callbacks to it when I construct it. This involved little more
> than moving some code around; and I had assumed that the user-visibible
> effect of this change would be nil. However, this appears to have had a
> significant impact on performance. Now when pressing a mouse button over
> the widget there is a significant delay before the widget response,
> where before it was virtually instantaneous. I'm also observing some
> crashes since making this change that suggest the event callbacks are
> now occurring on a different thread from before--surprising, but perhaps
> only because I don't know GTK well enough.

Are you able to test your programming approach with code taken from one 
of the example programs that ship with GtkGLExt? The examples just 
create a standard GtkDrawingArea and add GL capability to it along with 
standard signal callbacks.

A code snippet would help perhaps, to further clarify the problem you're 
having. I cannot see anything wrong with your approach since that's the 
approach we took when writing all the example programs. I suspect the 
problems are occuring may be because of the multithreaded nature of 
Mozilla and how it loads plugin modules.

Alif.