-
Notifications
You must be signed in to change notification settings - Fork 112
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
#1937: Fix layers settings for internal layers #1943
Conversation
}, | ||
{ | ||
"name": "selectedLayer", | ||
"path": "gnresource.selectedLayer" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dsuren1 is it possible to use just one of gnResourceSelectedLayerDataset
or selectedLayer
or do they are different?
Could you investigate on where the gnResourceSelectedLayerDataset is used and if it can be replaced by selectedLayer
, thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@allyoucanmap It seems each holds a different data. selectedLayer
holds selected node (layer) and selectedLayerDataset
holds dataset info available in mapLayers
by selected node
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the dataset fetch is asynchronous, there is a visual transition between TOCItemSetting
and the LayerSetting
plugin as the dataset is being retrieved. Therefore, I believe we should proceed with the current implementation as agreed
(cherry picked from commit 89a25af) Co-authored-by: Suren <[email protected]>
Description
This PR fixes the layer settings component used for internal layers
Issue