Hi folks!

Has anyone brought up this glitch in the POV for windows editor?

To reproduce the glitch, make sure you have v3.5 and then

1) go into Editor--EditorPreferences--Language/Tabs and turn OFF
   (uncheck) "Convert Tabs to spaces while typing"

2) Create a new file (File--NewFile)

3) On line 1, press your <TAB> key once and type ABCDEFG

4) On line 2, type ABCDEFG

5) On line 3, press your <TAB> key once and type ABCDEFG

6) Position your cursor in between C and D on line 1 and then play
   with your up and down arrows, the cursor should not stay within
   the same column when on line 2.

If this has been brought up, I'm sure I'll here about it otherwise
I should also hear about it :)

-- 
(MIKA) Marc Champagne
marcch.AT.videotron.DOT.ca
Montreal, CANADA

Post a reply to this message

Not sure I'm doing exactly as you had done.

If a New file isn't saved first it behaves differently than when saved, and
you didn't say which language scoping the editor is set to. Mines set to
POV-Ray and to follow that. Also, the Edit menu Constrain Caret to Text
matters. What I noticed in checking on this though is that the Caret didn't
jump to the same character position on line 3. If the file isn't saved,
meaning it doesn't comply with the settings yet I guess, the position shifts
left once for each line. If saved first then written, the position shifts
only at the 3rd line while staying aligned for the 1st and 2nd because of
the "ABCDEFG" already being aligned.
When looking at Show White Space the indentation appears to be correct.
--
Farewell,
Bob

"Marc Champagne" <nos### [at] pleasecom> wrote in message
news:Xns### [at] 204213191226...
>
> To reproduce the glitch, make sure you have v3.5 and then
>
> 1) go into Editor--EditorPreferences--Language/Tabs and turn OFF
>    (uncheck) "Convert Tabs to spaces while typing"
>
> 2) Create a new file (File--NewFile)
>
> 3) On line 1, press your <TAB> key once and type ABCDEFG
>
> 4) On line 2, type ABCDEFG
>
> 5) On line 3, press your <TAB> key once and type ABCDEFG
>
> 6) Position your cursor in between C and D on line 1 and then play
>    with your up and down arrows, the cursor should not stay within
>    the same column when on line 2.

Post a reply to this message

"hughes, b." <omn### [at] charternet> wrote in
news:3d9b2000@news.povray.org: 

> Not sure I'm doing exactly as you had done.
> 
> If a New file isn't saved first it behaves differently than when
> saved, and you didn't say which language scoping the editor is set to.
> Mines set to POV-Ray and to follow that. Also, the Edit menu Constrain
> Caret to Text matters. What I noticed in checking on this though is
> that the Caret didn't jump to the same character position on line 3.
> If the file isn't saved, meaning it doesn't comply with the settings
> yet I guess, the position shifts left once for each line. If saved
> first then written, the position shifts only at the 3rd line while
> staying aligned for the 1st and 2nd because of the "ABCDEFG" already
> being aligned. When looking at Show White Space the indentation
> appears to be correct. --

Thanks Bob,

I was getting that effect on a saved file with POV-Ray scoping.

"Constrain Caret to Text" did the trick, I have seen this option a many
of times and even looked it up in the help a few times but was unable to
figure out what it meant. (Caret=Cursor). 

Marc

Post a reply to this message

Marc Champagne <nos### [at] pleasecom> wrote in 
news:Xns### [at] 204213191226:

> "Constrain Caret to Text" did the trick, I have seen this option a many
> of times and even looked it up in the help a few times but was unable to
> figure out what it meant. (Caret=Cursor). 

That's called "Virtual Space"... Ie. the caret moves freely in the window 
space, and if you start to type while on the left of a line end, the editor 
will add spaces to fill the gap.
I don't like this mode, so I set the above option as soon as I can...
Now, other people like it, as they hate to see the caret jumps from a line 
end to another. This is a feature request for Scintilla, but nobody seems in 
a hurry to implement it :-)

Note: caret != cursor, at least on GUI environments (it may be true on Dos 
without mouse support...).
Cursor = mouse position indicator.
Caret  = current text input position.

-- 
--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--
Philippe Lhoste (Paris -- France)
Professional programmer and amateur artist
http://jove.prohosting.com/~philho/

Post a reply to this message

Philippe Lhoste <Phi### [at] GMXnet> wrote in
news:Xns### [at] 204213191226: 

> Note: caret != cursor, at least on GUI environments (it may be true on
> Dos without mouse support...).
> Cursor = mouse position indicator.
> Caret  = current text input position.

Well I've always seen it described as the current cursor position, it's
the first time I hear about "the caret" in my 20+ odd years of
computing.

Shesh, there is always something new to learn... 

Thanks

-- 
(MIKA) Marc Champagne
marcch.AT.videotron.DOT.ca
Montreal, CANADA

Post a reply to this message

Marc Champagne <nos### [at] pleasecom> wrote in 
news:Xns### [at] 204213191226:

> Philippe Lhoste <Phi### [at] GMXnet> wrote in
> news:Xns### [at] 204213191226: 
> 
>> Note: caret != cursor, at least on GUI environments (it may be true on
>> Dos without mouse support...).
>> Cursor = mouse position indicator.
>> Caret  = current text input position.
> 
> Well I've always seen it described as the current cursor position, it's
> the first time I hear about "the caret" in my 20+ odd years of
> computing.

Well, that's perhaps because you have so much experience... Before graphical 
interface, I suppose only "cursor" was used. With GUI, people had to 
distinguish them.

> Shesh, there is always something new to learn... 

Yes... Actually, I really started to make the difference after starting to 
contribute to the Scintilla open source project. That's not so long ago.

-- 
--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--=#=--
Philippe Lhoste (Paris -- France)
Professional programmer and amateur artist
http://jove.prohosting.com/~philho/

Post a reply to this message