10 Replies Last post: Apr 4, 2006 4:29 PM by Jesper Sahner Pedersen  
Jesper Sahner Pedersen   102 posts since
Apr 24, 2006
Currently Being Moderated

Mar 23, 2006 8:25 PM

Problems with ChildBrowserSample-example

Hi!

 

I am trying out the ChildBrowserSample-example.

 

First problem:

In the code I put a System.out.println() before and after the waitChild1()-call:

...

System.out.println("Before..");

// execute operation that opens child and get reference to the opened child (new method)

WebBrowser child = waitChild1(browser, element);

System.out.println("After..");

...

 

I wonder why the second System.out.println() is never reached?

 

 

Second problem:

Is the WebBrowser.trackChildren()-method deprecated? In the ChildBrowserSample-example it is only mentioned in the waitChild2()-method, which is described as the "old method".

 

 

Regards,

Jesper

Vladimir Ikryanov TeamDev Ltd. 404 posts since
Apr 24, 2006
Currently Being Moderated
1. Mar 29, 2006 4:16 PM in response to: Jesper Sahner Pedersen
Re: Problems with ChildBrowserSample-example

Hi,

 

1. In our environment we have not to reproduce this problem. The second System.out.println() is always reached. Please make sure you are using the latest version of JExplorer - 1.6.

 

2. The WebBrowser.trackChildren() method is not deprecated. And the waitChild2() method it just an alternative way of creating and retrieving the child instance.

 

Vladimir Ikryanov TeamDev Ltd. 404 posts since
Apr 24, 2006
Currently Being Moderated
4. Mar 30, 2006 3:35 PM in response to: Jesper Sahner Pedersen
Re: Re: Re: Re: Problems with ChildBrowserSample-example

Hello,

 

I managed to reproduce this problem. It happens if the child window is closed before the content of the page is loaded.

 

So you need to wait until the content of the page is fully loaded (you should see the Message Dialog).

 

Vladimir Ikryanov TeamDev Ltd. 404 posts since
Apr 24, 2006
Currently Being Moderated
7. Mar 31, 2006 3:30 PM in response to: Jesper Sahner Pedersen
Re: Re: Re: Re: Re: Re: Re: Problems with ChildBrowserSample-example

This error is not caused by JExplorer, but rather by Microsoft Office's Speech and Handwriting Recognition. In order to continue using JExplorer, you will need to disable this Microsoft feature.

 

To disable the Speech and Handwriting Recognition

 

   1. Click "Start" button at the bottom left of Microsoft Windows.

   2. Click "Control Panel."

   3. Click "Add/Remove Programs."

   4. Click "Microsoft Office."

   5. Click on the "Change" button

   6. Browse to "Office Shared Features."

   7. Click on "Alternative User Input."

   8. For both the Speech and Handwriting Recognition, select "Not available."

 

Once this is disabled, the CiceroUIWndFrame messages disappear. Also, please check this Microsoft support site for a more detailed set of steps to remove these tools:

http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;326526

Vladimir Ikryanov TeamDev Ltd. 404 posts since
Apr 24, 2006

Hi,

 

For receiving the newWindow events JExplorer 1.6 uses the DWebBrowserEvents2.NewWindow3 (http://msdn.microsoft.com/workshop/browser/webbrowser/reference/ifaces/dwebbrowserevents2/newwindow3.asp ) method instead the DWebBrowserEvents2.NewWindow2 (http://msdn.microsoft.com/workshop/browser/webbrowser/reference/ifaces/dwebbrowserevents2/newwindow2.asp ).

 

But the NewWindow3 is only available in Microsoft Windows XP Service Pack 2 (SP2) or later (http://msdn.microsoft.com/workshop/browser/webbrowser/reference/events/newwindow3.asp ).

 

So, if you use the Windows XP and  in your environment the Service Pack 2 not installed, please do it.

 

Vladimir

More Like This

  • Retrieving data ...