 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote:
> 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.
Big Yes !
I would love the extra feature. Sounds VERY usefull.
Thank you POV-Ray Team.
K.Tyler
P.S. Who is usualy the voice behind the povray.org admin team
Just curious
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
K. Tyler wrote in message <35E5EF50.D8F5CA81@pacbell.net>...
>povray.org admin team wrote:
>
>> Does anyone find the new editor in POVWIN beta 6 to be an improvement ?
>>
YES!! It seriously kicks ass over the previous one!
>> 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.
>
That would be a big bonus!
>P.S. Who is usualy the voice behind the povray.org admin team
>Just curious
>
AFAIK, It's Chris Cason.... I could be wrong.. I know it's a Chris. =)
--
Twyst -------------------------------------------
twysted mynd - for pov-ray news, reviews and tutorials
http://twysted.net
e-mail: twy### [at] twysted net
---------------------------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>Does anyone find the new editor in POVWIN beta 6 to be an improvement ?
Me!
>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.
Another VERY useful, but probably more difficult to implement feature
would be to set the cursor on a declaration of an identifier. For
example if one have
sphere {
0, 1
texture { T_Stone2 }
}
a right click on "T_Stone2" allows going to its declaration. This
declaration could be above in the same file or in a previously
included file, so the code has to be parsed for it.
Bye,
Friedemann
Friedemann Schmidt
Fri### [at] Stonescom
Raytracing-Gallery: http://www.rz.fhtw-berlin.de/~s0049669/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 28 Aug 1998 00:33:54 GMT, povray.org admin team
<new### [at] DESPAMpovrayorg> wrote:
I've been wondering about this. Does the POV news server really have a big
problem with spam? It doesn't seem like it would be my first stop for
addresses if I wanted to spam.
>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.
I really like the new editor. I've grown to love the editor in Visual
Studio, and this one works a lot like it. For that reason, it certainly
_seems_ better than the old editor. I also like that editdll.dll now seems
to be written in a C variant, so that increases the chances that we'll be
able to do interesting things with the insert menu. :)
BTW, count me as interested. I love new features.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
par### [at] my-dejanewscom (Ron Parker) wrote:
>On Fri, 28 Aug 1998 00:33:54 GMT, povray.org admin team
> <new### [at] DESPAMpovrayorg> wrote:
>
>I've been wondering about this. Does the POV news server really have a big
>problem with spam? It doesn't seem like it would be my first stop for
>addresses if I wanted to spam.
Some people cross-post messages to their 'real' news server. I've seen some
replies to messages from this server turn up on USENET. Also, sometimes people
crosspost to external servers, or just copy messages. Either way, the email
addresses can get out. Check out your local news server, and see if they have
any of the POVRAY.* groups. There's a good chance they will (they'll be empty,
but at some stage they got created).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
big YES to the two questions!
I still do not like some features, but I won't complain - yet :) I'll give
the new editor all the chances (and time) to convert me.
I am collecting a small list of bugs, and I will send it as soon as I
feel it to be complete.
BTW such problems as 'save as command doesn't provide
the old file name as default, nor is in the old directory', are to be
sent as a bug report by email, or to be posted here
as a feature proposition ?
Good day to everybody,
Sincerely,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>BTW such problems as 'save as command doesn't provide the old file name
>as default, nor is in the old directory', are to be sent as a bug report
>by email, or to be posted here as a feature proposition ?
Either. Posting here as a feature proposition is a better idea.
The 'save as' feature has now been modified to work as expected.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote:
> 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.
One major difference between 3.01 and 3.1b6 is the saving speed.
I was working on a file today that was about 6.5 megs in size.
3.01 was able to save after changes in about 2 sec.
3.1b6 was able to save after changes in about 10 - 15 seconds
At least a 10:1 difference.
K.Tyler
My system:
pentium 166 128 megs of ram windows 95 b
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <35e5f9d1.4652950@news.povray.org>, new### [at] DESPAMpovrayorg
(povray.org admin team) wrote:
> 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.
>
It's a big improvement, thanks for doing it. The new feature would be very
useful as well.
Ian Armstrong
iar### [at] cixcouk
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 ?
>
Are you kidding? This is the best thing that's happened to me since I came
back from vacation at the seaside. Here's a list of the 'little' things that
made me really love it:
- the way the 'home' key works...
- block indent
- match brace
- etc.
And a thing that disturbs me (not enough for a bug report, though): the
default output file type seems to be sys (.BMP). Since .BMPs are written
backwards POV makes an full-sized (900k for 640x480 -ua) empty file and goes
on... OK, but when I instaled POV I started playing around with demo scenes
at 800x600 +sp8 and was kinda bewildered where my HDD space had gone ... and
then I saw about 50 megs of .BMPs. I looked through the manual and the .INIs
and didn't see a notice of sys being default output file type. If this is
so, please document this change or make .TGA default (as it was).
>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.
Sounds good. What if the .INC is recursive ? <G> Anyway, this will probably
help add a nice feature: what about highlighting undeclared identifiers as
you type (to save some nerve?)
Congratulations to the Team on the great job they've done with beta6!
Regards,
--Peter
pet### [at] usanet
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
As soon as I installed and ran the new version
I really liked it. For me, it has a much better feel
to it. A big Thank You to the POV Team for this
great program. The new feature also sounds good.
Please keep up the great work.
David Young
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I agree -- the new editor is an excellent upgrade!
However, there are still features in emacs in POV mode
that make that, to me, preferable. Pardon me if I
am missing features in the current POV-W9x editor.
The features are:
1. Indent-line indent-region and indent-buffer :
automatically set indentation of a line, region,
or the entire buffer
2. Parenthesis matching : when a closing parenthesis is typed,
the curser briefly highlights the matching opening parenthesis.
If a closing parenthesis is typed after an opening bracket,
for example, a warning is issue. AFAICT, the POV-W9x editor
only does parenthesis matching on highlighted parentheses,
which interrupts typing.
However, the color code and auto-indentation of the POV
W9x editor does provide a nice visual clue if parenthesis
matching is off, so I am being picky here.
Still, I can hardly complain -- the new editor is a real programming
editor and a huge improvement over the previous edition, which
itself was quite usable.
I add my thanks to those of others posted here.
Dan
David Young wrote:
>
> As soon as I installed and ran the new version
> I really liked it. For me, it has a much better feel
> to it. A big Thank You to the POV Team for this
> great program. The new feature also sounds good.
> Please keep up the great work.
>
> David Young
--
http://www.flash.net/~djconnel/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>1. Indent-line indent-region and indent-buffer :
> automatically set indentation of a line, region,
> or the entire buffer
What exactly do you refer to here ? You can block-indent an entire selection if
you want (just as easily as the entire buffer since there's a select all key).
So I presume you mean something else ?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote:
>
> Does anyone find the new editor in POVWIN beta 6 to be an improvement ?
>
While the old editor was good and usable, calling the new one an
"improvement"
is a gross understatement, IMHO. The new editor's features represent a
quantum
leap over the old one...three cheers for the POV-Team!!!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The new povwin editor really is great. And, as everything,
as always, as everywhere, it can get even better. For me,
it should involve solving these bugs, including these
suggestions:
BUGS
* intellimouse support? what intellimouse support?
* state flashs in info bar
* 'open' button disabled on unmodified file... but
not the menu command
* ctrl+] match brace shorcut can't work on an belgian
azerty keyboard (you have to press ctrl+alt+$ to get
a ], so you can't add a ctrl over this), and I can't
change the shortcut
* shift+click doesn't select
* open and save dialogs sometimes give focus to other
applications on closing
* the end of a render sometimes takes focus from an other
application (particulary the help)
* = isn't highlighted (either as an assignement or as a
logical operator)
* copy on no selection does copy an empty string (logical
but not usual)
* Render/Edit setting/render (alt C) does render the previously
saved file, bypass the save dialog and the quit-bugging-me.
SUGGESTIONS
* return of the 'open in' command
* 'save' and 'save as' in the context menu
* ability to select and copy text in message window
* many 'strange' shorcuts if you have such standards
as MS Office, Adobe products or Macintosh's command
shortcuts:
redo - ctrl+y
close - ctrl+w
print - ctrl+p
replace - ctrl+h (ctrl+shift+F3 ???)
Is it so difficult to get all shorcuts customisable?
* toolbars are a bit too big. I would redesign them this
way if I could: move two help buttons to the 'main'
toolbar, remove theCD's and web sites buttons (but keep the
corresponding commands in the Help menu) and remove the
pretty but totally useless render animation.
* does anybody use the 'overwrite' mode? What is it usefull
for? If nobody use this, I would gladly see it desappear,
as I am always confused whenever I turn it on - always
by accident.
* move 'older files' at the end of the file list
* regroup the 'editor' menu with the 'options' menu
* still no command line editor
* a better and clearer structure for the help
Here are two last suggestion that I know are in conflict
with actual pov team orientation. (I know because I am not
the first to post about them). But I do not understand the
pov team position, as all they said was something like 'no,
we won't'. I do not say that there isn't a good reason, I
just ask what are the practical, design or programing
reason for an answer I do not understand. Maybe I am
missing the point? (Hey, saying 'no, we have enough work as
it is' is a very good reason... an excellent one. And an
unarguable one.)
(1) Why can't the 'quit bugging me' feature be kept from
session to session?
(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). This means: snap to the end of
line clicked in 'vacuum', left and right arrows can jump
to the previous or next line, don't add space at the end
of lines when inserting a carriage return in the 'vacuum'.
The 'select anywhere' feature could be used with
ctrl+click, like the collumn selection (this would be
coherent). Or you could toggle edit modes.
As always, all these suggestions reflect an user approach,
not a programmer's one.
By the way, did you try these wonderfull features or the
new editor?
* tab or shif-tab (= 'back-tab') a selection
* collumn selection (ctrl+drag)
* cut, copy and paste of collumns selection
* click'n'drag a selection
And let all say a big 'THANK YOU POV-TEAM' for their
thruly remarquable work.
Sincerely,
Philippe
P.S. I wrote earlier that I'll give the new pov editor
some time before asking anything... well, I did: I worked
two full days with it since (but as I do not have network
access on my computer I have to wait before posting, that
explains the missing day).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Philippe Debar wrote:
> SUGGESTIONS
One addition from me. Return start/stop rendering option
to right click menu.
> * ability to select and copy text in message window
agreed
**Also allow arrow key scrolling in main message window
> redo - ctrl+y
Leave ctrl+y alone It's fine the way it is.
> * toolbars are a bit too big. I would redesign them this
> way if I could: move two help buttons to the 'main'
> toolbar, remove the CD's and web sites buttons (but keep the
> corresponding commands in the Help menu) and remove the
> pretty but totally useless render animation.
I agree.
BUT I suspect that the pov team has their own agenda
for having them where they are. The cost of maintaining the
POV-Ray home page and running their own news server is
expensive. I suspect they are trying make it easier for people
to access and remember the locations of products and companies
that help with financial support for these wonderful privileges
and if that's the case I for one can live with it.
> * does anybody use the 'overwrite' mode? What is it useful
> for? If nobody use this, I would gladly see it disappear,
> as I am always confused whenever I turn it on - always
> by accident.
Yes I use it and please leave it alone
> * move 'older files' at the end of the file list
No ! No! No ! Leave it alone. I keep several .inc files open at all times
which allows easy cut and paste of common statements.
I don't want them moving all over the place. I like them stationary
and left were and in what order I put them.
> * a better and clearer structure for the help
Yep !
Which is to say I really liked the help system in
POV-Ray 3.0x and the new help system is confusing
and difficult to navigate. If I have to RTFM I need to
find the information so I don't have to ask stupid questions.
If anything return to a single scrollable help file instead
of a page to page style in use now.
> Sincerely,
> Philippe
K.Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello again
K. Tyler wrote in message <35E9A7F9.5C9D3914@pacbell.net>...
>> redo - ctrl+y
>Leave ctrl+y alone It's fine the way it is.
Yes, that's why I concluded with 'can't we really change
*all* shorcuts, please, mister Pov; pleeaasse'
>BUT I suspect that the pov team has their own agenda
>for having them where they are. The cost of maintaining the
>POV-Ray home page and running their own news server is
>expensive. I suspect they are trying make it easier for people
>to access and remember the locations of products and companies
>that help with financial support for these wonderful privileges
>and if that's the case I for one can live with it.
As I do not have network access on my computer,
each time I press the button mistakenly (once or twice a day),
I get this ******* MS connection wizard.
But if it mean supporting the pov team, thay can put as many
buttons as they want, I'll accept them gladly.
>> * 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).
>> * 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;-)
Good night everybody, sleep tight!
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote:
>
> >1. Indent-line indent-region and indent-buffer :
> > automatically set indentation of a line, region,
> > or the entire buffer
>
> What exactly do you refer to here ? You can block-indent an entire selection if
> you want (just as easily as the entire buffer since there's a select all key).
> So I presume you mean something else ?
Err.... I missed this one.
I would deserve a RTFM, except there is no M yet :).
Dan
--
http://www.flash.net/~djconnel/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>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 :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>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] flashnet> 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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] hotmailcom> 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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dear admin team member,
you wrote in message <35eb5934.93688056@news.povray.org>...
>The 'click anywhere' feature of the editor is internal to the editor
control
>and is not able to be changed by us.
I want to thank you for all the answers you provide. The more so when I
do so much dumb suggestions. I knew this feature would be at best quite a
lot of work and didn't even expect an answer. In such cases I expect the
normal and tacit answer to be 'no'.
That's very agreable to get an answer. But it make me almost afraid to post
my
wildest dreams... Next time you'll see such a crazy request from me, don't
answer;
but use the time of the answer to get a cup of coffee (or tea, or a slice of
pizza,
or whatever...) instead. That will make me much happier.
Thanks to the whole team,
Povingly,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ooops, sorry
>The 'click anywhere' feature of the editor is internal to the editor
>control and is not able to be changed by us.
I forgot I specifically asked for an answer on this one...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Philippe Debar" <phi### [at] hotmailcom> wrote:
>Ooops, sorry
>
>>The 'click anywhere' feature of the editor is internal to the editor
>>control and is not able to be changed by us.
>
>I forgot I specifically asked for an answer on this one...
After some discussion with the author of the edit control we've worked out a
way to add this. It'll be in the next beta (or the release if there's no next
beta).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote in message
<35f031e9.215343587@news.povray.org>...
>"Philippe Debar" <phi### [at] hotmailcom> wrote:
>
>>Ooops, sorry
>>
>>>The 'click anywhere' feature of the editor is internal to the
editor
>>>control and is not able to be changed by us.
>>
>>I forgot I specifically asked for an answer on this one...
>
>After some discussion with the author of the edit control we've
worked out a
>way to add this. It'll be in the next beta (or the release if there's
no next
>beta).
WOOOW THANKS THANKS THANKS
I do not know what to say...
Well a mighty thank to the author, and to the people who discussed.
Yee-haw
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team <new### [at] DESPAMpovrayorg> wrote in article
<35f031e9.215343587@news.povray.org>...
> "Philippe Debar" <phi### [at] hotmailcom> wrote:
>
> >Ooops, sorry
> >
> >>The 'click anywhere' feature of the editor is internal to the editor
> >>control and is not able to be changed by us.
> >
> >I forgot I specifically asked for an answer on this one...
>
> After some discussion with the author of the edit control we've worked
out a
> way to add this. It'll be in the next beta (or the release if there's no
next
> beta).
If you going to change this behavior please make it optional. I and, it
seems, many others, like it the way it is.
--
Scott Hill
Sco### [at] DDLinkscouk
Software Engineer (and all round nice guy)
Company homepage : http://www.ddlinks.demon.co.uk
"The best trick the devil ever pulled was convincing people he didn't
exist..."
- Verbal Kint.
"the Internet is here so we can waste time talking about nothing in
particular when we should be working" - Marcus Hill.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi!
Scott Hill wrote in message <01bdd7fe$a5889a60$8c00a8c0@shindo>...
> If you going to change this behavior please make it optional. I and,
it
>seems, many others, like it the way it is.
>Scott Hill
If you go back to the beginning of this discussion - I mean my post
that introduced this subject on this news group - that is 8 or 14
messages back in this thread, depending on how you count - that is
<35e99ce8.0@news.povray.org>, you'll see:
>(...)
>(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). This means: snap to the end of
>line clicked in 'vacuum', left and right arrows can jump
>to the previous or next line, don't add space at the end
>of lines when inserting a carriage return in the 'vacuum'.
>The 'select anywhere' feature could be used with
>ctrl+click, like the collumn selection (this would be
>coherent). Or you could toggle edit modes.
>
>As always, all these suggestions reflect an user approach,
>not a programmer's one.
I would never dream of asking anyone to remove a feature from pov...
only the possibility to turn it off...
And I understood that's what the pov-team proposes to do.
Cheers!
Povingly,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote:
> "Philippe Debar" <phi### [at] hotmailcom> wrote:
>
> >Ooops, sorry
> >
> >>The 'click anywhere' feature of the editor is internal to the editor
> >>control and is not able to be changed by us.
> >
> >I forgot I specifically asked for an answer on this one...
>
> After some discussion with the author of the edit control we've worked out a
> way to add this. It'll be in the next beta (or the release if there's no next
> beta).
What exactly is going to be added? I can't make it out - will "normal mode" be
optional?
Thanks
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
povray.org admin team wrote:
> "Philippe Debar" <phi### [at] hotmailcom> wrote:
>
> >Ooops, sorry
> >
> >>The 'click anywhere' feature of the editor is internal to the editor
> >>control and is not able to be changed by us.
> >
> >I forgot I specifically asked for an answer on this one...
>
> After some discussion with the author of the edit control we've worked out a
> way to add this. It'll be in the next beta (or the release if there's no next
> beta).
What exactly is going to be added? I can't make it out - will "normal mode" be
optional?
Thanks
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Fri, 4 Sep 1998 17:53:31 +0200, "Philippe Debar"
<phi### [at] hotmailcom> wrote:
>>(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). This means: snap to the end of
>>line clicked in 'vacuum', left and right arrows can jump
>>to the previous or next line, don't add space at the end
>>of lines when inserting a carriage return in the 'vacuum'.
>>The 'select anywhere' feature could be used with
>>ctrl+click, like the collumn selection (this would be
>>coherent). Or you could toggle edit modes.
>>
Well, I suppose you are calling "normal" behaviour the inability to
place the cursor past the end of a line of text, as in the older POV
editor. I actually prefer the new method myself, but I had already
been using another editor that behaves in this way. In that editor,
there is an option in the user settings that either allows or prevents
cursor placement past the end of the line. I would slightly prefer
that to having to hold Ctrl or anything else whenever I wanted to
place the cursor past the current end of the line.
Then again, I have also done a lot of scripting where the physical
layout of the code was important, because I was also employing
column-mode editing of similiar lines. It was frequently handy to add
generous amounts of white space to some of the shorter lines of code,
in order for the statements in those lines to physically line up with
similiar statements in a line above it. Sometimes I wanted to add
white space to the current end of a line, and then add a few
additional characters. Being able to simply click past the current end
of the line is a nice short cut, especially if I'm simultaneously
changing every line in a 6Meg mesh file, using cloumn-mode selection
techniques.
Later,
Glen Berry
Vice Project Coordinator
The Internet Movie Project (IMP)
Homepage: http://www.algonet.se/~jhubert/MovieProject/index.html
To reply via personal email, remove the "X" from Xno### [at] ezwvcom
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello...
John Wingfield wrote in message <35F03516.36EC29E0@kcl.ac.uk>...
>What exactly is going to be added? I can't make it out - will
"normal mode" be
>optional?
And others are wondering... so I collected the relevant posts:
Philippe Debar wrote in message <35e99ce8.0@news.povray.org>...
>The new povwin editor really is great. And, as everything,
>as always, as everywhere, it can get even better.
>(...)
>Here are two last suggestion that I know are in conflict
>with actual pov team orientation.
>(...)
>(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). This means: snap to the end of
>line clicked in 'vacuum', left and right arrows can jump
>to the previous or next line, don't add space at the end
>of lines when inserting a carriage return in the 'vacuum'.
>The 'select anywhere' feature could be used with
>ctrl+click, like the collumn selection (this would be
>coherent). Or you could toggle edit modes.
povray.org admin team wrote in message
<35eb5934.93688056@news.povray.org>...
>The 'click anywhere' feature of the editor is internal to the editor
control
>and is not able to be changed by us.
povray.org admin team wrote in message
<35f031e9.215343587@news.povray.org>...
>After some discussion with the author of the edit control we've
worked out a
>way to add this. It'll be in the next beta (or the release if there's
no next
>beta).
So, it does seem that the team plans to implement a toggle or an
access key to switch between the two modes.
I know nobody stated this explicitly, but it is logical from the flow
of the posts, the more so because:
* Many people ask for the actual mode, me included
there are many cases where it is very usefull;
* I don't see why they would remove a feature of pov -
that would be trashing perfectly good work ;
* They wrote ADD, not remove or change.
I hope this clear things a bit,
Thank you everybody,
Povingly,
Philippe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
