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

Positionning conflict between cadastrapp pane and urbanisme pane #181

Open
rgoffinet opened this issue Jun 22, 2023 · 6 comments
Open

Positionning conflict between cadastrapp pane and urbanisme pane #181

rgoffinet opened this issue Jun 22, 2023 · 6 comments

Comments

@rgoffinet
Copy link

Environment : portail-test.sig.rennesmetropole.fr
Versions : mapstore2-georchestra 2022.02.00 & 2022.02.02

When using the plugin urbanisme (https://github.com/sigrennesmetropole/geor_urbanisme_mapstore), if i open cadastrapp and then close it, the urbanisme's buttons and the mapstore toolbar container stays where the left end of cadastrapp pane were.

cadastrappVSurbanisme

@Gaetanbrl
Copy link

@Gaetanbrl
Copy link

Gaetanbrl commented Jun 22, 2023

@rgoffinet @MaelREBOUX Same behavior with toolbar if you remove urbanisme plugin from the context ?

@rgoffinet
Copy link
Author

@Gaetanbrl A similar behavior happens with the plugin "signalement"

cadastrappVSsignalement

@Gaetanbrl
Copy link

Gaetanbrl commented Jul 10, 2023

oh !
I guess an update of map layout missing on close.

UPDATE_MAP_LAYOUT action is required to update toolbar / searchbar location on setup or close.

On setup :

type: 'MAP_LAYOUT:UPDATE_DOCK_PANELS',

On close (tearDown) :

export const cadastrappTearDown = (action$, store) =>

@landryb
Copy link
Member

landryb commented Jul 5, 2024

is it still an issue or that's been fixed at some point ?

@rgoffinet
Copy link
Author

It is still an issue. We haven't yet been able to test the modification proposed by Gaetanabrl.

On the other hand, the conflict with signalement has been solved with this commit sigrennesmetropole/geor_signalement@421a676. This might help to solve this problem.

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

No branches or pull requests

3 participants