Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add map-projectionchange event. #911

Merged
merged 7 commits into from
Nov 15, 2023

Conversation

prushforth
Copy link
Member

@prushforth prushforth commented Nov 10, 2023

Closes #910

  • Delete map projection attrChgCallbk from triggering map-change event. Allow map-extent to react to map-projectionchange event, enable/disable according to projection match.
  • Change initialization logic for opacity, so that layer- and map-extent opacity value is maintained through map-projectionchange event.
  • Remove MapMLLayer.validProjection attribute and flawed logic.
  • Prettier formatting change only in multipleExtents.test.js
  • Remove use of validProjection by layer context menu, was wrong anyway(?)
  • Add waitfortimeout of 500ms in customTCRS.test.js (100ms was not enough)
  • Add test for simple projection change.
  • Add test for opacity through map-projectionchange - quite laggy, needed to waitfortimeout(1000) (at least)
  • Fix history after map-projectionchange not possible need to rewrite history
  • Update map-extent connectedCallback to throw if the units="projection_name" projection_name value is not a defined projection via mapml-viewer.defineCustomProjection

prushfor and others added 3 commits November 10, 2023 16:43
from triggering map-change event. Allow map-extent to react to 
map-projectionchange event, enable/disable according to projection match.

Change initialization logic for opacity, so that layer- and map-extent
opacity value is maintained through map-projectionchange event.

Remove MapMLLayer.validProjection attribute and flawed logic.

Prettier formatting change only in multipleExtents.test.js

Remove use of validProjection by layer context menu, was wrong anyway(?)

Add waitfortimeout of 500ms in customTCRS.test.js (100ms was not enough)

Add test for simple projection change.
updating in time. Skip test of history after map-projectionchange, pending
full rewrite of history api tbd.
@prushforth prushforth merged commit 5150ba3 into Maps4HTML:main Nov 15, 2023
1 check passed
@prushforth prushforth deleted the map-projectionchange branch October 3, 2024 18:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Changing projection on a map, a layer with 2 map-extents does not adapt to new projection
3 participants