Skip to content

v1.8.0
Compare
Choose a tag to compare
@Son-HNguyen Son-HNguyen released this 01 Oct 13:21
· 333 commits to master since this release
v1.8.0
4c3d2db

Release v1.8.0 demo link

NEW

  • It is now possible to display your own information about your web client in a splash window that is loaded upon start.
    By default:

    • All contents (HTML, CSS, JS) are to be stored in the folder splash.
    • The HTML page is named SplashWindow.html and all belonging CSS and JS files must be declared/imported in the HTML file.
    • On mobile devices, the web client will search for the HTML page named SplashWindow_Mobile.html and display it instead.
      If such file does not exist, the default SplashWindow.html shall be used.
      Thus, if you wish to display your own contents modified for mobile devices,
      make sure to save them in the additional SplashWindow_Mobile.html file.

  • If the contents of the splash window are however stored somewhere else,
    the splash window can be declared as a set of string parameters in the web client URL using the following syntax:

    &splashWindow=url=<path_to_your_html_file>&showOnStart=<true|false>

    where:

    Parameter Description Allowed values Default Value
    url A valid path to the HTML file An absolute path if the HTML file is located in another domain or a relative path if the HTML file is located in the same project folder as the web client splash/SplashWindow.html
    showOnStart A boolean that determines whether the splash window should be shown upon start or not true or false true

  • The splash window has two buttons: Close and Ignore (or Do not show again). the former closes the splash window but does not prevent it from appearing again if the page is reloaded.
    Therefore, the latter button can be used to suppress the splash window from appearing again.
    Note that a cookie named ignoreSplashWindow will be created locally, which tells the web client whether or not to display the splash window based on the user's choice.

  • The configurations of the splash window (url and showOnStart) can be modified using the main toolbox in the web client. There, you can also overwrite or remove the current splash window.

    • Once the flag showOnStart has been modified and saved, it will overwrite the cookie ignoreSplashWindow.
      For example, a checked showOnStart flag in the toolbox will set the cookie ignoreSplashWindow to false again, regardless of the cookie's value.
    • On the other hand, the cookie ignoreSplashWindow will be priortized against the string parameters in the web client URL. For example, a web client with URL ...&showOnStart=true will display the splash window on the first load.
      After the option Ignore (or Do not show again) is selected, the cookie ignoreSplashWindow with value true is created. This cookie will prevent the web client from displaying the splash window again on the next load, as expected, even if the web client URL has the parameter showOnStart=true.
      To reset or remove the cookie, simply go to the main toolbox and set the flag showOnStart accordingly, since the flag has the highest priority and will overwrite the current value of the cookie.

  • The splash window as well as other information about the web client are displayed in an additional tab in the Cesium's default navigation help popup triggered by the "question mark" button in the top right corner of the screen.

FIXES
  • Fixed rotation/heading of glTF v0.8, see e049ffd.
  • Fixed a bug that prevented highlighting of Cesium3DTileFeatures, see 01b0241.
  • Fixed a bug that caused selected geometries to stay highlighted even after deselecting, see a161234.
  • Fixed a bug that prevented retrieving properties of Cesium3DTileFeatures, see 20e0a8e.
  • Fixed a bug that prevents selection of 3D tiles objects, see ce18aab.
  • Fixed (un)highlight of 3D tiles objects, see 6be754c.
  • Fixed a bug when multiple alert windows appear at the same time, see d5c5f4e.
  • Fixed the size of Cesium's error dialog that could not be displayed correctly on mobile devices, see 763df04 and f0705bc.
  • Fixed a bug that prevented the web client from reading user's ion token correctly, see 59a62f6.
  • Fixed point size of point cloud datasets, see 73c7c84.
UPDATES
  • It is now possible to fly the camera directly to a recently highlighted/clicked entity, even if no cityobjectsJsonUrl is present.
    The cityobjectsJsonUrl is a JSON file containing information about location and coordinates linked to object IDs and thus was used prior to v1.7.1 to enable flying to such entities.
    Starting with v1.7.2, the web client shall store recently highlighted/clicked entities in a dictionary with {id, target entity} tuples as its key-value-pairs.
    This way, a direct fly to hightlighted/clicked entites is possible without having to rely on the cityobjectsJsonUrl.
    However, this will not work if the stored entities are not yet loaded or have been unloaded (e.g. typically when the camera has been moved to a different location).
    In this case, the web client will fall back to using the cityobjectsJsonUrl. See 4c7bcfd.
  • Selected as well as highlighted objects from different layers can now be listed together in the
    Choose highlighted object as well as Choose hidden object dropdown list (prior to v1.7.1 this was not possible since only objects from the same active layer were allowed). See 4c7bcfd.
  • Clicking the home button will fly the camera to the position and orientation defined in the URL.
    If no corresponding parameters exist or are found in the URL, the camera shall fly to the default location and orientation defined in Cesium. See, 4f23407.
  • Updated JQuery to v3.3.1, see a60b900.
  • Updated Flatpickr v4.5.1 to v4.6.2, see 6d9d570 and a56076e.
Assets 2
Loading