> Perhaps better would be to move to the beginning (up) or end (down)
> of the current code block, under the theory that a code block is
> roughly the source code equivalent of the paragraph (except, of
> course, that they're hierarchical).
Correct me (gently as usual) if I am wrong: a block is a If .../... End If
(While, Try, For, ...) statement. What happens when there is no statement in the
current Code (Event, MenuHandler, Method, whatever) ?
BUT, your argument is fine (if I understand it correctly) if there is two cases:
there is a Code Block near the Cursor position, place the cursor at the start of
the Code Block (or the end or whatever can be the best if it is not the start of
the Code Block) and if there is no Code Block, Option-Top Arrow will place the
cursor at the beginning of the first visible line on the top of the Code Editor
Window, Option-Down Arrow same but first character of the last visible line...
After all and I think that was Johnathan who wrote that, this is a Code Editor
of a development environment, not a World Processor. Using a shortcut that help
the Developer productivity _cannot_ be against anything, but _IS_ for its user help.
I do not know if the line continuity character (_) is in the HIG, but this sort
of things improve line readings on a development environment (was there in
HyperCard for example *); at first, when people were asking, I think that I was
not seeing its utility, but when it was here, I understand and now I can use it
on a regular basis...
Cheers,
Emile
* even if HyperCard is not a good example
[EMAIL PROTECTED] wrote:
Subject: Re: Please, put back Option-Up-Arrow and Option-Down-Arrow From: "Joseph J.
Strout" <[EMAIL PROTECTED]> Date: Wed, 22 Feb 2006 13:23:28 -0700 At 7:44 AM -0600
2/22/06, Jonathan Johnson wrote:
Actually, the behavior described is not standard Mac OS behavior. The
standard behavior is to move the insertion point "To the beginning of
the current paragraph, then to the beginning of the previous
paragraph" for option-Up, and the opposite for option-Down. Since
REALbasic isn't a text editor, we don't have the concept of
paragraphs, so we treat each line as a paragraph.
I didnt answer to that at first because below was a nice proposition that I
liked. But now, I can say that I do not care about what is called: "the behavior
described is not standard Mac OS behavior".
Yes, as a recent Windows user (I still use my PowerBook to code) and a new Linux
user (to be), I do not care. Worst, PageUp and PageDown (on Windows) do exactly
what REALbasic 5.5.5 and lower does (what I asked). I have to say that I do not
like that; as a Macintosh user, I use Page Up / Page Down - sometimes - to read
some code above or below the current Cursor location and come back to code
there, so moving _MY_ cursor is like a knowck on my fingers: it hurts ;)
However, I understand your answer and like you I feel that this does not apply
to a programming environment.
One Click: place the Cursor at the Click x,y location,
Two Clicks: moves the Cursor at the Click x,y location and select the word found
there,
Three Clicks: moves the Cursor at the Click x,y location and select the line
found there,
Four Clicks: moves the Cursor at the Click x,y location and select the paragraph
found there.
Since "REALbasic isn't a text editor, we don't have the concept of paragraphs,
so we treat each line as a paragraph." how do you implement that ? :)
Also, how do you explain the ability to choose (select) the whole Code Block in
a click ?
NOooooooooooo, do not remove it...... THIS IS A DEVELOPMENT environment and it
does not have to follow the strict HIG rules when the digression is here as a
developer helper (increase the developer productivity in any way) and while this
is explained in the documentation.
It's good to have some fun ;) Thanks...
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
