Subscribe to this thread
Home - Cutting Edge / All posts - Manifold 9.0.180.3
adamw


10,447 post(s)
#03-Jun-23 16:13

9.0.180.3

manifold-9.0.180.3.zip

SHA256: 5d4174da81bd6b5c1262b171a62927bbfcaea1ea8619be7466ea0d37d8f5d558

manifold-viewer-9.0.180.3.zip

SHA256: 8d0d90b86dbfe058dde855a09133faa497ffd6961755f34d23b76daf94908137

sql4arc-9.0.180.3.zip

SHA256: 6a375fb38cdd87c0a0656b29f81a1b308ed9fb779833e7e17c8527c878c9a9d6

adamw


10,447 post(s)
#03-Jun-23 16:14

Changes

The ODBC driver supports extra connection options required by newer versions of Excel 365.

The HTTP server supports -cx:xxx and -cy:xxx command line options that specify the image size. The maximum allowed value for each option is 4096. If neither CX nor CY is provided, the image size is 800x800. If only CX or CY is provided, the image size is CXxCX or CYxCY. If both CX and CY are provided, the image size is CXxCY.

The HTTP server better handles invalid requests with attached content. (Previously they were being rejected later than they could have been.)

Attempting to create a second instance or reinitialize an existing instance of the Javascript control provided by the HTTP server does nothing. (There can currently be only one instance of the Manifold Javascript control per web page. This limitation will be removed in the future.)

If the size of the Javascript control provided by the HTTP server is less than 200x200 pixels, the control reduces to a static image. (The toolbar is turned off because there is no space. Panning and zooming using the cursor are turned off because there is no way to get back to the original extent plus the image might be too small to perform panning and zooming in general.)

The HTTP server shows the description of the served component below its name. (When providing the description for a map, make sure to edit the description of the map component instead of the description of the active layer.)

The Javascript control provided by the HTTP server puts the toolbar directly onto the top edge of the map without any gaps, to better use the available space.

The Javascript control provided by the HTTP server adjusts the UI for devices with a touch screen (eg, phones): toolbar buttons are made bigger, hover effects for toolbar buttons are turned off, panning and zooming the map using the cursor is turned off, clicking on the map re-centers it.

The HTTP server includes available locations in the configuration data for the Javascript control. The Javascript control shows locations provided via the configuration data in a dropdown menu and allows zooming to them.

The HTTP server includes layers that can be turned on or off in the configuration data for the Javascript control. The Javascript control shows layers provided via the configuration data in a dropdown pane with checkboxes and allows turning them on or off and then saving changes using the Apply button. The list of layers that can be turned on or off is composed according to the following rules:

  • if the served component is a map, top level layers can be turned on or off and layers inside layer groups cannot (the distinction allows one to have both layers that can be controlled via the web UI and layers that cannot),
  • if the served component is not a map, its only layer cannot be turned on or off.

The HTTP server uses the following priorities for the image cache: full view > any other view, default layers > some layers turned on or off.

Changes to the HTTP server endpoints:

  • /config - a new endpoint, returns the configuration data for the served component as plain text, this is useful as a reference when setting up a web site,
  • /map - supports a new parameter: layermod=hXXsYY... to turn layers on or off, the value of the parameter is a string of 'hXX' and 'sYY' commands where (a) 'hXX' forces the layer with the ID equal to XX to be hidden, and (b) 'sYY' forces the layer with the ID equal to YY to be shown unless it has to be hidden due to the current scale being outside of the layer's min-max scale range, layer IDs are found in the configuration data for the component.

End of list.

artlembo


3,404 post(s)
#03-Jun-23 20:04

Very easy, cool. I can see where you guys are going with the endpoint idea, and anticipate that we’ll be able to add WMS or WMST at some point.

Using the layermod parameter just brings up an image with no controls. Any thoughts on sending an HTTP request to only show a single layer that is part of a Map component, and having that work inside the control?

adamw


10,447 post(s)
#05-Jun-23 17:04

There's a Layers button in the control that allows turning the layers on and off. Underneath, it uses the layermod parameter. So you can use the feature both inside the control and outside of it.

artlembo


3,404 post(s)
#05-Jun-23 20:34

Yes, I saw that. Very cool. What I meant was that when I send a url with

…./map?layermod=‘s01’

It simply brings up a static image it would be nice to have the map come up in the control, but only show that particular layer

The reason is I would like to have a Map component with say 100 layers in it, but an html page that would let people click on an html link and just view that particular layer I don’t want to use up all the ports for each of the 100 layers I don’t mind that once in the map page they can turn on other layers, but this would be a nice way to start the creation of a portal to explore individual drawings by putting them all in a single map and creating a url that only shows one or more of the layers

adamw


10,447 post(s)
#09-Jun-23 18:25

Oh, we'll do it differently - we'll allow serving multiple components from the same MAP file, they will have different URLs. (You'll have to either list the components you want served, or perhaps tell 'serve all components' using something like '*'.)

Manifold User Community Use Agreement Copyright (C) 2007-2021 Manifold Software Limited. All rights reserved.