-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
Popup children display - Add an option to use the component lizmap-features-table #4667
Comments
I think this is an interesting addition.
If this new feature could be improved with points above, I think that this new component could totally replace the actual behaviour. Otherwise IMHO is better to leave to editors the choiche Thanks! |
Indeed 👍 It's been a while I had this feature in mind. Happy to start shaping it.
At present, for 3.8, only the web component has been added. It is not yet used in LWC, but can be freely used by "power-users" in the parent popup (QGIS tooltip HTML configuration). I plan to integrate it further more in future 3.9
Nothing is done yet, but this will indeed be the desired behaviour when automatically used in child popup(s)
Not yet, I have in mind to fully respect the drag & drop designer for :
Fully agree.
You are welcome, thanks a lot for sharing your thoughts |
Much more #4407 I have a PR ready for this but cannot be tested yet because of this behavior 3liz/qgis-lizmap-server-plugin#82 |
Is your feature request related to a problem? Please describe
In the context of a relation between a parent layer and a child layer, Lizmap allows at present to configure the parent popup to display the children popup underneath.
Since the recent addition of #4502 we should propose a way to use this component instead. It will look like :
Describe the solution you'd like
Either remove the present behaviour, or propose a new checkbox or a radio button to let the editor choose between showing the list of child popups or use the new compact table.
cc @rldhont @nboisteault @Gustry @mind84
The text was updated successfully, but these errors were encountered: