Right before this object's constructor, try to create the image object on its own. If that doesn't work, try to create the image as the first think your app does. If that does work, you've got something in your app breaking the image. If that doesn't work, you have a bad image. If they both work, then you've got a problem somewhere in your object, so try allocating the Image at different points of the constructor, until you've found the command that breaks the Image loading process.
You can also try a different Image, to see if the SPECIFIC Image is the problem there, or if any image is a problem. IOW, at this point we have no idea whether or not it's a GWT problem, and (since you haven't given us the code necessary to replicate the problem) noway to help you if it IS a GWT problem. Greg On Feb 24, 5:54 am, "Alex D." <[email protected]> wrote: > Still no idea guys? > > On Feb 23, 6:19 pm, "Alex D." <[email protected]> wrote: > > > Hi, > > The code below will not finish (gets hanged in the Image constructor): > > > public class ATest extends GWTTestCase { > > // ..... init code .... // > > > public void testShouldNotHang () { > > // Create an empty image > > final Image img = new Image(); > > } > > > } > > > The hang happens on Image:237 => > > Event.sinkEvents(image.getElement(), Event.ONLOAD); > > > Now, I'm not trying to test the Image constructor, but I have complex > > components that cannot be modified for testing purposes, and the > > happen to have Image inside. I have searched but I couldn't find any > > answer ... nobody else had this issue? > > > Thanks -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
