 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> 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
|
|
| |
| |
|
|
|
|
| |
