|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gRRosminet <pov### [at] les-charlesnet> wrote in message
news:405dbde9@news.povray.org...
> the stable release of qtpoveditor v0.3.0 has been published. The
> ressources package have also been updated with a new help.
>
Hmmm, maybe I'm missing something obvious, but how do I tell it where the
help files are? It only looks at http://qtpoveditor.sf.net
Somewhere local would be nice...
RG
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
A copy of the help is in the ressources package. If you want to use them
instead of the online version, y'ou'll have to modify line 506 in file
"poveditmainwindow.ui.h"
gonzo wrote:
> gRRosminet <pov### [at] les-charlesnet> wrote in message
> news:405dbde9@news.povray.org...
>
>>the stable release of qtpoveditor v0.3.0 has been published. The
>>ressources package have also been updated with a new help.
>>
>
>
> Hmmm, maybe I'm missing something obvious, but how do I tell it where the
> help files are? It only looks at http://qtpoveditor.sf.net
>
> Somewhere local would be nice...
>
> RG
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> http://qtpoveditor.sf.net
Excellent work, thank you for this editor! It compiled without problem
under linux slackware 9.1, gcc 3.3.3, qt 3.2.3. I use it every day now.
Here is the list of my wishes (is this the right place to post them?):
1. Insert menu entries are not recursive. I mean if the insert menu path
contains a deep structure of directories only the first level *.txt
files are displayed in the insert menu (see below)
2. When quitting, even if all files are saved, the editor keeps asking
about open files and if it should save some of them. When there are
unsaved files, this is the normal behavior, but otherwise is somewhat
annoying.
3. It would be nice to have a small preview for the insert menu items
where there is a *.bmp file available (standard windows povray
distribution does that) - it helps a lot the beginners like me :-)
(maybe also an option somewhere to disable this feature if it is
annoying for more experienced users)
4. after running povray it shoud be nice to have a non modal windows
displaying the resulted image. Right now I use am image viewer and
refresh the image every povray run, but again, it is a little bit
annoying. Kpovmodeler has a window like this which displays the image
being rendered while it is rendered, with a progress bar and a speed
indication (in kpixels/sec). I know kpovmodeler is a kde program, but
maybe Qt can do that also.
Concerning the first point, I wrote a (very) small patch to parse
recursively the insert menu path and display *.txt files found as nested
menu items. I use insert menu add-on(s) from Friedrich Lohmueller site
and some others and the directory structure is recursive many times deep.
If anyone is interested, drop me a mail.If Thierry accepts patches maybe
I can send it to him (it's really a small modification).
Happy raytracing for all!
Marin
--
-----------------------------------------------------------------------------
Replay-to address is fake. Please replace it
with mferecat (at) numericable (dot) fr.
-----------------------------------------------------------------------------
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gRRosminet wrote:
> A copy of the help is in the ressources package. If you want to use them
> instead of the online version, y'ou'll have to modify line 506 in file
> "poveditmainwindow.ui.h"
Thanks, I'll check it out. The online help is too unreliable on my
tempermental dial-up.
This would be good to have as an option in the preferences.
Everything else looks great! Thanks for your considerable effort!
RG
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Marin Ferecatu wrote:
>
>> http://qtpoveditor.sf.net
>
>
> Excellent work, thank you for this editor! It compiled without problem
> under linux slackware 9.1, gcc 3.3.3, qt 3.2.3. I use it every day now.
>
> Here is the list of my wishes (is this the right place to post them?):
>
> 1. Insert menu entries are not recursive. I mean if the insert menu path
> contains a deep structure of directories only the first level *.txt
> files are displayed in the insert menu (see below)
> Concerning the first point, I wrote a (very) small patch to parse
> recursively the insert menu path and display *.txt files found as nested
> menu items. I use insert menu add-on(s) from Friedrich Lohmueller site
> and some others and the directory structure is recursive many times deep.
> If anyone is interested, drop me a mail.If Thierry accepts patches
> maybe I can send it to him (it's really a small modification).
==> Of course I want it ! actualy, I was realy hurry ti get something
working, but I can remember that doing something recursive would not be
a hard work to do it. I'll integrate it into the source if you've done it !
>
> 2. When quitting, even if all files are saved, the editor keeps asking
> about open files and if it should save some of them. When there are
> unsaved files, this is the normal behavior, but otherwise is somewhat
> annoying.
==> I know, I know ... this was the easiest solution. I think I'll do
something for this
>
> 3. It would be nice to have a small preview for the insert menu items
> where there is a *.bmp file available (standard windows povray
> distribution does that) - it helps a lot the beginners like me :-)
> (maybe also an option somewhere to disable this feature if it is
> annoying for more experienced users)
==> If you do it, it'll be integrated, but I don't think I'll do it
(previews are frequently non-representative)
>
> 4. after running povray it shoud be nice to have a non modal windows
> displaying the resulted image. Right now I use am image viewer and
> refresh the image every povray run, but again, it is a little bit
> annoying. Kpovmodeler has a window like this which displays the image
> being rendered while it is rendered, with a progress bar and a speed
> indication (in kpixels/sec). I know kpovmodeler is a kde program, but
> maybe Qt can do that also.
==> Of course, this can be done using QT. Personnaly, I use the povray
output with the "Pause when done" option. Perhaps a viewer could be added.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> 4. after running povray it shoud be nice to have a non modal windows
>> displaying the resulted image. Right now I use am image viewer and
>> refresh the image every povray run, but again, it is a little bit
>> annoying. Kpovmodeler has a window like this which displays the image
>> being rendered while it is rendered, with a progress bar and a speed
>> indication (in kpixels/sec). I know kpovmodeler is a kde program, but
>> maybe Qt can do that also.
>
>
> ==> Of course, this can be done using QT. Personnaly, I use the povray
> output with the "Pause when done" option. Perhaps a viewer could be added.
I also like the image window of the windows version and I tried to patch
your editor to do the same. I ran into problems because the image
POV-Ray produces is only a valid image file when the render has finished
(which is quite understandable). There are image-viewers out there which
can display "broken" (=unfinished) PNG-images (which was the only type I
tested it with), but unfortunately I could not get Qt to display such
files. If anyone finds a solution for this problem, I'd be happy to do
the rest :)
If this would mean to much work another option would be to display only
the finished image. This is however not really a solution, IMHO, but a
bad workaround.
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just checked the KPOVModeler sources to see how they do it. Seems (was a
quick glance, ok? *g*) that they are first buffering the image without
writing it to disk and later convert it after the user selected the
image output format.
Looks like just another workaround to me. But OTOH, it may be impossible
to do it in another way without patching POV-Ray (what would be a bad
idea, because you could not use other patches like MegaPOV with the editor).
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Just got another feature idea:
how about supporting povray-patches? Let the user add all the patches
like MegaPOV or mlPOV or whatever he has installed in some config file,
together with the new keywords which they introduce. Add a list box to
the render options to let the user decide which render engine he wants
to use.
This would also allow users for example to use stable releases and beta
releases on the same file without much hassle. I know that one can
simply change the command line for POV-Ray, but hey, this is about
usability (wow, I actually managed to use this "new" oh-so-hot-topic in
a real discussion *g*).
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If I well understand, you would like to be able to create profiles
containing the keywords list and the command ?
Florian Brucker wrote:
> Just got another feature idea:
>
> how about supporting povray-patches? Let the user add all the patches
> like MegaPOV or mlPOV or whatever he has installed in some config file,
> together with the new keywords which they introduce. Add a list box to
> the render options to let the user decide which render engine he wants
> to use.
> This would also allow users for example to use stable releases and beta
> releases on the same file without much hassle. I know that one can
> simply change the command line for POV-Ray, but hey, this is about
> usability (wow, I actually managed to use this "new" oh-so-hot-topic in
> a real discussion *g*).
>
> Florian
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> If I well understand, you would like to be able to create profiles
> containing the keywords list and the command ?
Yep. Although the keywords aren't that important, but would be simply a
nice thing to have :)
Florian
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |