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