How do I disable the new pop-up command history window?

32 visualizaciones (últimos 30 días)
Mark
Mark el 7 de Mayo de 2014
Comentada: Ronald Bloom el 6 de Mayo de 2021
How do I disable the new pop-up command history window in 2014a? I absolutely hate it and never want it to appear again.
  3 comentarios
Oleg Komarov
Oleg Komarov el 28 de Oct. de 2014
Apparently, it is not possible anymore. I tried to dock it and then manually undocking. It just goes into pop-up mode.
Adam Schwartz
Adam Schwartz el 9 de Jul. de 2015
From Mathworks support:
1. On the Home tab, in the Environment section, click Layout.
2. Then, under Show, select Command History. It has three options - Docked, Popup or Closed.
Select the docked/closed option to avoid the command history window from popping up subsequently.

Iniciar sesión para comentar.

Respuesta aceptada

Justin
Justin el 7 de Mayo de 2014
Editada: Justin el 7 de Mayo de 2014
One way is to press the up arrow in the command window so the history shows up. Then you can right click the bar on the top of the history popup window and choose to dock the window.
That should solve any annoyance with the default behavior.
Also, to change it back or open it if it is closed you can go to:
Home Tab > Environment Section > Layout > Command History
and choose docked, popup, or closed. (The section names are at the bottom of the tab area.)
  6 comentarios
Peter Cervelli
Peter Cervelli el 18 de Ag. de 2019
Thanks for sharing this tip!
Note to Matlab developers:
It is absolutely essential that new features like this can ALWAYS be disabled. Although I acknowledge the utility of features like the pop-up command history window for some users, many others see them as unwelcome distruptions to long-established work flows. Speaking of which, if anyone knows how to disable the inane tooltips in the Matlab editor, I would love hear about it. I can't tell you how many times these useless messages have blocked the content I really wanted to see.

Iniciar sesión para comentar.

Más respuestas (2)

Jon Northup
Jon Northup el 24 de Ag. de 2019
It IS still possible to have the Command History become a seperate stand-alone window. Justin helped me find the best way (successful using 2018b):
  • Starting with Command History "undocked" (misnomer, actually invisible, but waiting to pop up).
  • Type <Up Arrow> to invoke the history pop-up.
  • Option 1: Note the pop-up has a little bar along top edge with little rectangle in center. Left click on the bar to drag the window onto your desktop. This will tear it off to become its own window.
  • Option 2: Note the little circle with down arrow in upper right corner of the pop-up. Click it to expand sub-menu, near bottom of list click "Detach" to become its own window.
  • The detached Command History window can be closed (hidden) or docked again whenever desired.
Enjoy!

Leena Singh
Leena Singh el 19 de Mayo de 2017
Thank you Justin for vocalising your dislike of this and thank you Mathworks Suppport for showing how to squash it. I loathed the damn thing enough to consider reverting back to R2013 so i could go back to a pop-up free existence.
  2 comentarios
Jerry Olup
Jerry Olup el 25 de Mayo de 2018
Editada: Jerry Olup el 25 de Mayo de 2018
Fundamentally, I think the user would expect "undock" to actually undock the window rather than change the mode to popup. At times I have commands that I would like to select adjacent to the IDE.
Jon Northup
Jon Northup el 24 de Ag. de 2019
I agree that this new "pop-up" mode is not the same as "undock". If some people like it, it should be a seperate mode. Even the initial default is OK, but let me have an option to do it as before. "Undock" for the Command Window doesn't make it disappear, it just becomes its own stand-alone window. That seems more to me the natural sense of "undock", as it was in older versions, and is with competitor IDE's and tools.
I use multiple versions of MATLAB to generate code that has agency approval linked to the particular version of code generation tools used. That means when behavior issues like this change over time, I notice more than most, because it's right in front of me and I get frequent reminders. Usually, I can account for syntactical changes made over time so that scripts are backward-compatible to older versions. But having something change that can never be made to work like it did before just seems wrong.

Iniciar sesión para comentar.

Categorías

Más información sobre Entering Commands en Help Center y File Exchange.

Productos

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by