changing WMS Url needs to reset some options

Reimar Bauer reporter

edited description

2017-04-06T20:02:40+00:00

Joern Ungermann

I disagree with "update on changes". "update on changes", "transparent" and "cache" are options that are not server dependent. Typically a User sets these to a desired state and then switches between servers. Resetting them each time a server is changed (which may occur more often now as one doesnt need to request capabilities again) would be quite annoying.

I do not now, what "other values" refers to, but all WMS server specific buttons are disabled when the URL in the field is changed.

2017-04-07T06:24:18+00:00

Reimar Bauer reporter

I had the situation as I toggled between two urls by typing that "update on changes" tries something, but I haven't called get requirements. Nothing was disabled.

2017-04-07T21:38:50+00:00

Joern Ungermann

Okay, I see the issue. The problem is that changing the URL will trigger a call to get_map. This potentially triggers error conditions, if the URL is not valid, or the default conditions for the new URL are not valid for some reason.

One solution would be to disable the "update on changes". Certainly, one should trigger the get_map call, if the URL is not valid, i.e. if the get_map button is disabled.

2017-04-23T16:52:09+00:00

Joern Ungermann

Further investigation shows this to be a bug, potentially crashing the application. The state of the "get map" button is disregarded by the autoUpdate function in addition to some timing problems. This needs to be addressed in the stable version.