Order of Icons in Native Notebook toolbar is odd
See original GitHub issueWhat is the expected order of icons
-
Run All (added by vs code, when running all, this changes to
Stop
) -
Clear output (added by VS Code)
-
Interrupt Kernel (added by us) Enabled only when cells are running (kernel is busy)
-
Open Changes (added by VS Code - no idea why this is after our icon?)
-
Restart Kernel Enabled only when cells are running (kernel is busy)
-
Run Cell Above Enabled only when any cell other than 1st is selected
-
Run cell & below
-
Variable viewer
-
Export Notebook
-
Trust Icon (Red when not trusted, & green when trusted)
-
Specify Local or remote (used to toggle between local or remote jupyter connections)
-
Last (split editor) Added by VS Code
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Using the notebook bar - LibreOffice Help
The notebook bar shows a different way to organize controls and icons than a collection of straight rows of icons, displaying contextual groups...
Read more >Basics of Jupyter Notebook and Python | Packt Hub
The Toolbar contains icons for common actions. In particular, the dropdown menu showing Code lets you change the type of a cell. Following...
Read more >Solved: Anaconda Jupyter Notebook Layout - Esri Community
When an ipynb file is opened, it now looks like this. Many buttons are gone such as the stop button. Did I mistyped...
Read more >May 2021 (version 1.57) - Visual Studio Code
We added a notebook toolbar in the editor, in which you easily access actions like insert cell, run all cells or switch kernels....
Read more >Solve problems with Jupyter Notebooks - coursera.support
Error messages such as Method Not Allowed appear in the toolbar area. · The last save or auto-checkpoint time shown in the title...
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
Unless we have good reason to change it (one reason may be VS Code limitations), it should remain the same as webview had it:
If we cannot mimic what we had due to VS Code limitations we can file a bug on them.
Validating as I believe our current toolbar is what we expect: