 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>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. the shortcut assigments that you can
change are only the ones managed by the editor common control. we have
no way of adding to them (apart from modifying the source to cmax101.dll,
which would be a hassle). and we don't see it as being logical to have
TWO dialogs for setting shortcuts (one for us, one for the editor).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Philippe Debar wrote:
> Hello again
>
> >> * does anybody use the 'overwrite' mode?
> >Yes I use it and please leave it alone
>
> Well, that's what question are for. Without any irony of any
> sort, what do you use it for? I did never find any case where
> it would be usefull... and I'm always open to a new editing
> technique (even more if it means I'll gain time).
>
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.
> >> * move 'older files' at the end of the file list
> >No ! No! No ! Leave it alone.
> Well, I do not use it (yet) - so you surely know better. But
> I am not sure we understood each other perfectly: I meant
> 'move the older file commant just above the exit command',
> (this was my orderly self speaking), and not as my message
> read 'move the content of...' Well, anyway, I am bickering;-)
Sorry I thought you were referring to the open file windowsand not the menu file
history log.
> Good night everybody, sleep tight!
ZZZzzzzz !
> Philippe
K.Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote:
>
> >Err.... I missed this one.
> >
> >I would deserve a RTFM, except there is no M yet :).
>
> It's always a good idea to spend time inspecting the menus and options dialogs
> of a new program (that's what I always do, even before I look at the manual).
> Menu captions can be most informative :)
Okay, RTFMAOD, then :).
Thanks for the correction,
Dan
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dan Connelly <djc### [at] flash net> wrote:
>povray.org admin team wrote:
>>
>> >Err.... I missed this one.
>> >
>> >I would deserve a RTFM, except there is no M yet :).
>>
>> It's always a good idea to spend time inspecting the menus and options dialogs
>> of a new program (that's what I always do, even before I look at the manual).
>> Menu captions can be most informative :)
>
>Okay, RTFMAOD, then :).
>
>Thanks for the correction,
To make things a bit easier, the Selection menu (off the Edit menu) has now
been changed so as to not be disabled when there's no selection. So you can pop
it up any time ; the individual items are disabled instead. This will make menu
exploration a bit easier for other users in the future.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sun, 30 Aug 1998 20:41:29 +0200, "Philippe Debar"
<phi### [at] hotmailcom> wrote:
> 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.
> print - ctrl+p
People print POV source?
>* 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.)
>(2) The editor behaviour which permits to select where
>there aren't any character is really great. But a normal
>text editor behaviour (like the last one) is more
>convenient most of the time (I kinda checked this, I
>watched myself working).
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, as in the following code
snippet:
sphere { <.333,.666,.999> .576 texture {color Red}};
sphere { <.888,.444,.333> .733 texture {color Green}};
I've just changed the radius in the first line to .576. 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.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ronald L. Parker wrote:
> 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, as in the following code
> snippet:
>
> sphere { <.333,.666,.999> .576 texture {color Red}};
>
> sphere { <.888,.444,.333> .733 texture {color Green}};
>
> I've just changed the radius in the first line to .576. 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.
Then you definatly should download beta6. It don't *^&#%@
do that no more no more.
And this pleases me immensely
K.Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
