 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi
Pleins de merci !
For the editor and corrections!
Great
Thanks
Martial
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote in message <35e5f9d1.4652950@news.povray.org>...
>Does anyone find the new editor in POVWIN beta 6 to be an improvement ?
>
>BTW If there is sufficient interest we will post a new editor DLL that has
one
>new feature added since the beta 6 release - it allows you to right-click
on a
>#include line and automatically open the file that is being included.
Everybody agrees: the new editor is GREAT. But if you really want to now
how good it is, try going back to the old one!
I had to... it's not an experience I care to reproduce.
Many, many, many thanks to the pov team
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
K. Tyler wrote in message <35E9F5F1.C88D004C@pacbell.net>...
>I have a line of code that says translate<333.001,555.557,1.001>and I want
to
>change to translate<444,222.557,1.111> instead
>of highlighting it, deleteing it, and retyping it or hitting the delete key
>9 times and retyping it I use the overwrite mode and with 9 keystrokes
>I'm done. Saves wear and tear on my decrepit old body.
I try this right away.
Bye!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ronald L. Parker wrote in message <35ea1c43.171513624@news.povray.org>...
>> redo - ctrl+y
>I've always thought the standard for redo was shift-alt-backspace.
>> close - ctrl+w
>This is, of course, ctrl-f4. Just because other apps can't follow the
>published UI guidelines is no reason for POV to follow suit.
Well, I believe these shorcuts came from the macintosh. This would
explain why they're present in Adobe products. And Microsoft adopted
them when they extended Office for the Mac. Many applications can use
several simulaneous shorcuts sets. E.g. povwin undo is alt-backspace as
well as ctrl+z.
>> print - ctrl+p
>People print POV source?
Yes, I do (but with Word, because printing isn't implemented yet in
beta 6).
>>* a better and clearer structure for the help
>I hadn't noticed that big a difference between the new (beta 5) help
>structure and the old (3.01) help structure. Did it change again in
>beta 6? (I haven't looked and don't have beta 6 at home yet.)
It didn't change much. Maybe the pov scene language help didn't change
at all (I don't remenber exactly). But the specific povwin help did change
a bit.
>I find "normal" behaviour annoying. Here's the situation that annoys
>me the most: I'm sitting in the middle of a long line that is
>identical in structure to another long line (....)
I really like the new editor, and I get more used to it. Anyway, I
proposed a toggle, so would it be implemented no one could loose
anyhing - apart from the people programing it :-) The 'click anywhere'
feature of the new editor is only annoying me because I set my 15"
screen on 1024*768 at least (I like to see as much code as possible
and big images) .
Tracingly,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello... how are you today?
Ronald L. Parker wrote in message <35ea1c43.171513624@news.povray.org>...
>> redo - ctrl+y
>I've always thought the standard for redo was shift-alt-backspace.
>> close - ctrl+w
>This is, of course, ctrl-f4. Just because other apps can't follow the
>published UI guidelines is no reason for POV to follow suit.
I believe these shorcuts (mine, not yours) came from the Macintosh.
This explains why you find them in Adobe's products (or simile). I think
Microsoft adopted them when they ported office to the Macintosh. This
is not a reason to start a jihad: many applications support these two
sets of shorcuts in parallel. E.g. pov's undo is alt+backspace and
ctrl+z.
>> print - ctrl+p
>People print POV source?
Yes I do. Sometimes it is usefull. (Printing isn't implemented in
beta6 - but the menu command is there already.)
>>* a better and clearer structure for the help
>I hadn't noticed that big a difference between the new (beta 5) help
>structure and the old (3.01) help structure. Did it change again in
>beta 6? (I haven't looked and don't have beta 6 at home yet.)
I am not sure the pov-ray scene language help did change from
beta5 to beta6. The specific povwin help did.
>>(2) The editor behaviour (...)
>I find "normal" behaviour annoying (...)
Well, each to his own. That's what is so good with toggle.
>(...) I want to
>cursor down to the next line and change the radius there as well.
>Nope, doesn't work. Cursoring through the blank line moves the cursor
>to the 'home' position and *^&#%@ leaves it there when I cursor to the
>next line.
I agree. But there are some 'standard' text editor that solve this (I can't
name
one from memory though) so it is _possible_. Anyway, the main reason why
the 'click anywhere' feature is bugging me is that I set my 15" screen to
1024*768 at least (I like to see as much code as possible and to have
big images with some room around for working).
Tracingly,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 31 Aug 1998 21:10:31 +0200, Philippe Debar
<phi### [at] hotmail com> wrote:
>Hello... how are you today?
Fine, thanks, and you?
>I agree. But there are some 'standard' text editor that solve this (I can't
>name
>one from memory though) so it is _possible_. Anyway, the main reason why
>the 'click anywhere' feature is bugging me is that I set my 15" screen to
>1024*768 at least (I like to see as much code as possible and to have
>big images with some room around for working).
I run 1152x864 on a 17" screen, so I know what you mean. But I've been using
Visual Studio for so long, I've gotten used to being able to click where I
want to go without having to wear out my spacebar. BTW, in case you hadn't
noticed, pressing the 'end' key moves you to the end of the line. If there
is spurious whitespace at the end of the line, pressing 'end' cycles you from
the real end of the line, to the last non-whitespace character, and back
again. If you're sitting after the last non-whitespace character (where
pressing end either once or twice puts you) and press shift-end, you can
delete all of the spurious whitespace with at most 4 keystrokes.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi
povray.org admin team wrote in message <35eaee8a.846657@news.povray.org>...
>>Yes, that's why I concluded with 'can't we really change
>>*all* shorcuts, please, mister Pov; pleeaasse'
>it's very difficult to do that.
Well, fair enough.
How can we manifest our appreciation of your work? I always feel like
the suggestions I post are hurting everybody and that my thanks can't
repair this.
Tracingly,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ron Parker wrote in message <35eafa89.0@news.povray.org>...
>>Hello... how are you today?
>Fine, thanks, and you?
>(...)
>BTW, in case you hadn't
>noticed, pressing the 'end' key moves you to the end of the line. If there
>is spurious whitespace at the end of the line, pressing 'end' cycles you
from
>the real end of the line, to the last non-whitespace character, and back
>again. If you're sitting after the last non-whitespace character (where
>pressing end either once or twice puts you) and press shift-end, you can
>delete all of the spurious whitespace with at most 4 keystrokes.
Wow - thanks!
I'm fine also ;-)
Bye!
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
One thing that I have missed is the MaxiMinimise
Button. Is it still around or have you gotten rid of it.
I did use it quite often.
David Young
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The 'click anywhere' feature of the editor is internal to the editor control
and is not able to be changed by us.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
