The latest version of GMapsFX has been released and includes a major bug fix and a few enhancements.
Last month I reported a bug that has been affecting users of GMapsFX on Mac OSX where the text appeared ‘garbled’. An example image is below.
The underlying issue is that the JavaFx WebView component on Mac OSX is rendering icons rather than letters for some websites, including Google Maps.
I receive a tweet from @ggeorgopoulos1 with a proposed work around that involves injecting CSS programatically into the page with the correct font. I’ve incorporated the code into the latest GMapsFX library and I am happy to say that it is working once again on Mac OSX!
Added a setKey() method to the GoogleMap compoment
This will allow a key to be set in the FXML and will eliminate the need to programatically set a key on the map object at runtime.
I have been receiving a lot of messages the last couple of months regarding the text in GMapsFX applications looking “garbled”, as illustrated in the screenshot below.
This is appears to only affect applications running on Mac OSX. GMapsFX makes use of the JavaFX WebView component under the hood, so I created a simple test app that loads Google Maps into a WebView to confirm the issue was the WebView component.
I filed a bug report with Oracle, but apparently this is a known issue that affects only some websites in WebView on Mac. Linux and Windows applications using the WebView component are unaffected.
So now getting the Lat/Long of a mouse click is a relatively straightforward process.
We tell the map we want to add a click UI event listener and pass in an event handler which handles a GMapMouseEvent event object. From that object the latitude and longitude of the event can be determined.
Currently the Lat/Long are the only properties available on the GMapMouseEvent object, but additional properties will be added as demand warrants.
Below is a screenshot of one of the example applications included with the GMapsFX project that illustrates how to capture the lat/long of a mouse click.
I’m a big believer in learning from my mistakes, but I’m an even bigger believer in learning from other people’s mistakes. Hopefully someone else will be able to learn from my mistakes.
This post is inspired by an issue that took me a number of days to track down and pin point the root cause. It started with NullPointerExceptions randomly be thrown in one of my applications. I wasn’t able to consistently replicate the issue, so I added an indiscriminate amount of logging to the code to see if I could track down what was going on.
What I found was that when I was attempting to pull a value out of a particular hashmap, the value would sometimes be Null, which was a bit puzzling because after initializing the map with the keys/values, there were no more calls to put(), only calls to get(), so there should have been no opportunity to put a null value in the map.
Below is a code snippet similar (but far more concise) to the one I had been working on.
Any guesses what happens when the code above is run?
Exception in thread "main" java.lang.NullPointerException
So what happened? The HashMap stores its keys by using the hashcode of the key objects. If we print out the hashcode when the ProductSummaryBean is first created and also after its read out of the DB we get the following.
Printing out the entire objects shows that while name, upc code, and price are all the same, the DecimalFormatter used for the price is different. Since the DecimalFormatter is part of the hashcode() calculation for the ProductSummaryBean, the hashcodes between the before and after versions of the bean turned out different. Since the hashcode was modified, the map was not able to find the corresponding ProductDetailBean which in turned caused the NullPointerException.
Now one may ask, should the DecimalFormat object in the bean been used as part of the equals() and hashcode() calculations? In this case, probably not, but this may not be true in your case. The safer way to go for the hashmap key would be to have used the product’s upc code as the HashMap key to avoid the danger of the keys changing unexpectedly.
I recently received a question regarding how to add the GMapsFX component to SceneBuilder, so it could be dragged and dropped onto the UI as its being constructed.
I thought I would address the question here since the good folks at Gluon have made it extremely easy to import custom components to SceneBuilder.
The first step is to click the small ‘gear’ icon just to the right of the Library search box and select the “JAR/FXML Manager” menu item from the popup menu.
Since the GMapsFX binaries are in the Maven Central repository SceneBuilder can directly download and install the component from there. Click the “Search repository” link in the Library Manager dialog box.
Next, enter “GMapsFX” into the Group or artifact ID text box, and click the “Search” button. You should get a search result with the com.lynden:GMapsFX artifact. Select the result and click “Add JAR”.
The GoogleMapView should be the only component available in the Jar file, select it and click the “Import Component” button.
Finally, you should get a confirmation that the library was imported into SceneBuilder.
At this point the GoogleMapView component should be visible in the “Custom” component section of the pallette, and ready to be dragged and dropped onto your UI. Due to the way the component is constructed, a map will not display in SceneBuilder or the SceneBuilder preview tool, but the proper FXML will be generated and the map will display when the program is run.
Mapping directions in a JavaFX application is easy with the Directions API that was recently introduced in GMapsFX. In this blog post I’ll walk through an example of setting up an application with a map and a couple of text fields, one which will be used for the trip origin and the second which will be used for the trip destination. When the user hits ‘Enter’ in the destination text field, the map will display the directions.
Starting off with the FXML file, we have an AnchorPane which contains the GoogleMapView and 2 TextFields. The AnchorPane has a controller assigned to it named FXMLController, and both components have an FX ID associated with them so they will be accessible from the FXMLController class. Also, the destination TextField has an action, “toTextFieldAction” associated with it, so this method will be called when the user hits the ‘Enter’ key in the TextField.
Next, I’ve cut up the relevant parts of the FXMLController class. The MapComponentInitializedListener interface needs to be implemented by the controller since the underlying GoogleMap doesn’t get initialized immediately. The DirectionsServiceCallback interface also needs to be implemented, although in this example I won’t be doing anything with it.
The GoogleMapView and the TextFields components from the FXML file are defined below and annotated with @FXML.
There is also a reference to the Directions Service as well as StringProperties to represent the ‘to’ and ‘from’ endpoints that the user will enter.
After the controller is created, its initialize method is called which will set the MapView’s initialization listener to the FXMLController as well as bind the ‘to’ and ‘from’ String properties to the TextProperties of their respective TextFields.
Once the map has been initialized, the DirectionService can be instantiated as well as a MapOptions object to set various attributes about the map. The options are then configured and a GoogleMap object can be instantiated from the map view. The directionsPane is a component which can be used to render the step by step direction text, in this example however, it won’t be displayed.
Finally, the action method defined in the FXML file when the user hits ‘Enter’ in the TextField is below. The method will call the getRoute() method on the DirectionsService class, passing in a boolean value which will define whether the route can be modified by dragging it, the map object, and the DirectionsRequest object.
Mapping an address in a JavaFX application is extremely easy with the Geocoding API that was recently introduced in GMapsFX. In this blog post I’ll walk through an example of setting up an application with a map and a text field. The map will recenter itself at whatever address or place the user types in the text field.
Starting off with the FXML file, we have an AnchorPane which contains the GoogleMapView and a TextField. The AnchorPane has a controller assigned to it named FXMLController, and both components have an FX ID associated with them so they will be accessible from the FXMLController class. Also, the TextField has an action, “addressTextFieldAction” associated with it, so this method will be called when the user hits the ‘Enter’ key in the TextField.
Next, I’ve cut up the relevant parts of the FXMLController class. The MapComponentInitializedListener interface needs to be implemented by the controller since the underlying GoogleMap doesn’t get initialized immediately. The GoogleMapView and TextField components from the FXML file are defined below and annotated with @FXML.
There is also a reference to the GeocodingService as well as a StringProperty to represent the address the user enters.
After the controller is created its initialize method is called which will set the MapView’s initialization listener to the FXMLController as well as bind the address property to the address TextField’s text property.
Once the map has been initialized, the GeocodingService can be instantiated as well as a MapOptions object to set various attributes about the map. Once the options are configured, a GoogleMap object can be instantiated from the map view.
Finally, the action method defined in the FXML file when the user hits ‘Enter’ in the TextField is below. The method will call the geocode() method on the GeocodeService class, passing in the value of the Address property as well as a callback method.
The callback will check the status of the results, and based on the outcome, will recenter the map at the latitude/longitude the user had entered.
A new version of GMapsFX has been released to bintray and Maven Central. The main feature in this version is to allow the use of custom marker/pin images, rather than relying on the default Google images.
A future blog post will demonstrate how to add custom markers to your GMapsFX application.