... the user friendly GPS tool


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Webstart error: 1.33 does not show map
#1
1.33 has a bug in the map display. It does not display the map and gives an error message "Failed to create ....<lots of java stuff>" and "reason: the native interface is not open".
Reply
#2
What is the exact error message?
--
Christian
Reply
#3
Failed to create chrriis.dj.nativeswing.swtimpl.components.NativeWebbrowser[1,29775659]

Reason:
The native interface is not open


in 1.32 the map works but some other crazy stuff is happening. For some reason or other I cannot move any waypoints anymore. I can delete existing waypoints just fine. The insert option on the RMB menu doesn't work. And also the "einfugen" button on the "insert positions" window doesn't work anymore. It used to put a waypoint in the center of the map. Now nothing happens.

I don't know what's going on. I have used 1.32 last week and I am sure all this worked fine. Has anything changed in the Google Maps API???
Reply
#4
(04.05.2010, 18:05)bekker Wrote: Failed to create chrriis.dj.nativeswing.swtimpl.components.NativeWebbrowser[1,29775659]

Reason:
The native interface is not open

And what is printed below that? Please send a screenshot.

(04.05.2010, 18:05)bekker Wrote: in 1.32 the map works but some other crazy stuff is happening. For some reason or other I cannot move any waypoints anymore.

The 1.32 routeconverter.html file in the %TEMP%\routeconverter\ directory is not compatible with the 1.33 version. Just delete it before switching back to an older version.

(04.05.2010, 18:05)bekker Wrote: I can delete existing waypoints just fine. The insert option on the RMB menu doesn't work. And also the "einfugen" button on the "insert positions" window doesn't work anymore. It used to put a waypoint in the center of the map. Now nothing happens.

Same reason as about.

(04.05.2010, 18:05)bekker Wrote: Has anything changed in the Google Maps API???

No, the Google Map API is versioned and thus changes that affect the client code can be minimized by selecting a specific API version.

I guess the following happend:
  • You used 1.32 and everything worked fine
  • You tried 1.33, which created a new routeconverter.html, but now something like a personal firewall is now blocking the map since it's a different binary and you see the error message.
  • You went back to 1.32 which now fails, too, since it does overwrite the 1.33 routeconverter.html file used to initialize the browser.
--
Christian
Reply
#5
I am new to Route Converter and downloaded it today with Webstart.

I got a similar result and can not use Google Maps. See the included screenshot.

I use Windows 7 (32 bit professional) with Firefox 3.7a4 a my default browser.

Firefox it self display Google Maps without any problems.

regards Ditmar


Attached Files Thumbnail(s)
   
Reply
#6
I am now testing it on a vista premium laptop and 1.33 works and shows the map. However when I zoom in the map the route does not get completely recalculated at certain zoom levels. Often only the part of the route that is visible is recalculated for that zoom level. You can see that in this case the total route distance shown above the waypoints list is now much shorter.

I did not see this behavior in 1.32.

Chera
Reply
#7
(09.05.2010, 10:42)rose28357 Wrote: I am new to Route Converter and downloaded it today with Webstart.
I got a similar result and can not use Google Maps. See the included screenshot.

Hi Ditmar,

please show the RouteConverter.log file (the FAQ explains where to find it).

(09.05.2010, 10:42)rose28357 Wrote: Firefox it self display Google Maps without any problems.

What about the Internet Explorer? And do you use a personal firewall?
--
Christian
Reply
#8
Here is the Log. I deleted the old log and then started RC and terminated it.

I use the Windows7 Firewall without any changes since installation.

Internet-Explorer is IE8 and can be started manually. Google Maps in IE8 is also running. So i assume basically its not an IE8 problem ?
Reply
#9
(09.05.2010, 11:12)rose28357 Wrote: So i assume basically its not an IE8 problem ?

I don't know, but I've found and fixed a problem: I forgot to copy a new Eclipse SWT libary version to the server. For me, it works now, and for you?
--
Christian
Reply
#10
Should we download this library or a new pre-release?

Chera
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)