Disabled toolbar items in RetroLab
See original GitHub issueDescription
This seems to be happening in RetroLab and is related to the app.commands.notifyCommandChanged();
trick added in https://github.com/jupyterlite/jupyterlite/pull/528.
It’s not reproducible on all page reloads.
Reproduce
Go to a JupyterLite website running 0.1.0b1
and open a notebook with RetroLab.
Context
Follow-up to https://github.com/jupyterlite/jupyterlite/pull/528
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
jupyterlab/retrolab - GitHub
Click the RetroLab button in the toolbar; or; View > Open in RetroLab from the menu. To access the main RetroLab tree (file...
Read more >Allow toolbar items to be disabled via binding in Angular
We would like to be able to disable toolbar items via binding instead of calling enableItems. Code should be able to look something...
Read more >retrolab - PyPI
Click the RetroLab button in the toolbar; or; View > Open in RetroLab ... An animation of a user using the command palette...
Read more >distracting environment - OSCHINA - 中文开源技术交流社区
Launching From an open notebook: Click the RetroLab button in the toolbar; ... menu item to Quote Tweets in the timeline UI improvements...
Read more >Corel PaintShop Pro 2022 User Guide
Removing flaws and objects with the Clone Brush or Object Remover . ... When docking is disabled, toolbars and palettes can float anywhere....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ha. Lablite. Will do some more digging but might be a tick…
Not sure 3.3.1 would fix it, the changelog doesn’t seem to mention anything related to it.
But we could still do the update to the 3.3.1 packages.