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
When switching from 3d viewport to 2d viewport using the changeView and trying to click on the settings button in the Map layers widget breaks the widget.
20241206-1207-48.2026521.mp4
Expected Behaviour:
The Map layers widget should be disabled in 2d Viewer.
Current Behaviour:
The Map layers widget is enabled in the 2d Viewer.
Proposed Solution:
Along with subscribing to the useActiveViewport hook. We should also subscribe to the onChangeView listener.
Version: 5.4.4
Version of iTwin.js: 4.8.0
Operating system: Windows
Browser: Chrome 131.0.6778.86
The text was updated successfully, but these errors were encountered:
afraj-attar
changed the title
[Map Layers Widget] Map Layers widget breaks in 2d Viewport
[MapLayers Widget] Map Layers widget breaks in 2d Viewport
Dec 6, 2024
I think after investigating a bit that the best approach is to mimic what property grid did with their handling of hiding their widget when the selection set is empty (found here)
which is to say the handling of this shouldn't be in the widget, but it should be in the UiItemsProvider in a wrapper of the widget provided therein because it should be the standard handling within the AppUi system that all consumers of the widget using AppUi would want to reuse
When switching from 3d viewport to 2d viewport using the changeView and trying to click on the settings button in the Map layers widget breaks the widget.
20241206-1207-48.2026521.mp4
Expected Behaviour:
The Map layers widget should be disabled in 2d Viewer.
Current Behaviour:
The Map layers widget is enabled in the 2d Viewer.
Proposed Solution:
Along with subscribing to the useActiveViewport hook. We should also subscribe to the onChangeView listener.
Version: 5.4.4
Version of iTwin.js: 4.8.0
Operating system: Windows
Browser: Chrome 131.0.6778.86
The text was updated successfully, but these errors were encountered: