Comments on: EditorMacro – assign a keyboard macro in the Matlab editor

By: Jason McMains

Jason McMains — Mon, 26 Oct 2009 03:28:58 +0000

in any version specific code I've written, I had actually accounted for the 7.0.1 issue by taking only the first 3 characters max, which would give me 7.0 or 7.5 etc. I had just heavily simplified for posting. so really line 2 should read:

if str2double(Mversion.Version(1:min([3 end])) >= 7

By: Mike Katz

Mike Katz — Fri, 23 Oct 2009 15:26:07 +0000

In reply to Yair Altman. True. It's on the file exchange for that purpose, but I understand. Just wanted to point it out, though.

By: Yair Altman

Yair Altman — Fri, 23 Oct 2009 14:38:24 +0000

In reply to Mike Katz. Unfortunately Mike, varLessThan was only introduced in recent Matlab releases, so if I have an older release I would get an error. Which brings me back to try/catch which works for all Matlab releases :-)

By: Mike Katz

Mike Katz — Fri, 23 Oct 2009 14:26:44 +0000

..forgot to mention that to @Jason that str2double is dangerous b/c some versions of MATLAB such as R14SP1 don’t have straightfoward numbers, it’s 7.0.1

By: Mike Katz

Mike Katz — Fri, 23 Oct 2009 14:24:40 +0000

RE: the try/catch case, the verLessThan function is meant to address providing version-dependent behavior.

By: Yair Altman

Yair Altman — Thu, 22 Oct 2009 23:41:01 +0000

Andrey – you are correct: try-catch should be used, but excessive use has drawbacks. I guess this is true for most things in life… As elsewhere, there isn’t a clear-cut definition of how much is “just right” – we should all apply judgment and common-sense.

By: Andrey

Andrey — Wed, 21 Oct 2009 12:58:25 +0000

Yair Hi!

There are also some reasons why using try-catch isn’t good in this case

1) Simple Code – The code is harder to understand.
2) Debugging – When using try-catch without taking a look at the caught exception, you might miss an error which isn’t related to Matlab version at all. Since you catch it, you will never see the stack in Matlab.
3) Case handling – You will eventually need another try-catch for the matlab 6 section, to handle other versions (not 6 or 7). So what you get is basically a lot of recursive try-catch, which makes the code even less understandable.

By: EditorMacro v2 - setting Command Window key-bindings | Undocumented Matlab

EditorMacro v2 - setting Command Window key-bindings | Undocumented Matlab — Fri, 21 Aug 2009 08:35:58 +0000

[…] The EditorMacro utility was extended to support built-in Matlab Editor and Command-Window actions and key-bindings. This post describes the changes and the implementation details. […]

By: Yair Altman

Yair Altman — Fri, 17 Jul 2009 14:01:34 +0000

In reply to Neil.

@Neil – In answer to your question, I posted a follow-up: http://undocumentedmatlab.com/blog/non-textual-editor-actions/

Removing text can be done using hDocument.delete(startPos,endPos)

Enjoy 🙂
Yair

By: Neil

Neil — Tue, 14 Jul 2009 20:29:35 +0000

Great post — one step closer into the black hole void of the matlab gui. Do you know of any way of running commands other than inserting text, for example, moving the cursor, deleting a word/line, or more dynamic text editing?