You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do any of the code contributors here know why the Composite layer types always are pinned to the zero element in the workbench?
I wouldn't mind, but it seems to be interfering with my FeatureInfoTemplate for another WFS layer used to creates chart and uses a csv for the source of the chart. TerriaJS seems to want to put the CsvCatalogItem (that represents a selected point in the WFS layer) in the zero workbench position too. It there any known work around for this clash? Thanks very much!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Do any of the code contributors here know why the Composite layer types always are pinned to the zero element in the workbench?
I wouldn't mind, but it seems to be interfering with my FeatureInfoTemplate for another WFS layer used to creates chart and uses a csv for the source of the chart. TerriaJS seems to want to put the CsvCatalogItem (that represents a selected point in the WFS layer) in the zero workbench position too. It there any known work around for this clash? Thanks very much!
Beta Was this translation helpful? Give feedback.
All reactions