 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
dick balaska <dic### [at] buckosoft com> wrote:
> I have released qtpovray-3.80.1 for Linux.
> https://github.com/dickbalaska/qtpovray/releases/tag/v3.80.1
great.
> It is also rumored to build and run on Slackware 14.1
"out of the box", no.
make[1]: Entering directory `/tmp/QTP/qtpovray-3.80.1/qt/libpovray'
g++ -c -include povray -pipe -O2 -march=native -mtune=native -fPIC -fPIC
-std=gnu++11 -w -D_REENTRANT -DQT_DEPRECATED_WARNINGS -DTRY_OPTIMIZED_NOISE
-DBUILD_X86 -DQT_NO_DEBUG -DQT_CORE_LIB -I. -I../../source -I../../platform/unix
-I../../platform/x86 -I../../unix/povconfig -I../../vfe -isystem
/usr/include/qt5 -isystem /usr/include/qt5/QtCore -I.
-I/usr/lib64/qt5/mkspecs/linux-g++ -o
tmp/QTP/qtpovray-3.80.1/source/base/image/openexr.o
...../../source/base/image/openexr.cpp
In file included from ../../source/base/image/openexr.cpp:49:0:
/usr/include/OpenEXR/ImfRgbaFile.h:50:23: fatal error: ImfHeader.h: No such file
or directory
#include <ImfHeader.h>
^
compilation terminated.
make[1]: *** [tmp/QTP/qtpovray-3.80.1/source/base/image/openexr.o] Error 1
make[1]: Leaving directory `/tmp/QTP/qtpovray-3.80.1/qt/libpovray'
make: *** [sub-qt-libpovray-make_first-ordered] Error 2
still needs adding the 'INCLUDEPATH += "/usr/include/OpenEXR"' line to the
'libpovray.pro' file to make it work. not to worry though, it is easy to patch
from the (unwritten as yet :-)) qtpovray.SlackBuild script.
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/21/2018 09:36 AM, jr wrote:
>
>> It is also rumored to build and run on Slackware 14.1
>
> "out of the box", no.
>
> make[1]: Entering directory `/tmp/QTP/qtpovray-3.80.1/qt/libpovray'
> g++ -c -include povray -pipe -O2 -march=native -mtune=native -fPIC -fPIC
> -std=gnu++11 -w -D_REENTRANT -DQT_DEPRECATED_WARNINGS -DTRY_OPTIMIZED_NOISE
> -DBUILD_X86 -DQT_NO_DEBUG -DQT_CORE_LIB -I. -I../../source -I../../platform/unix
> -I../../platform/x86 -I../../unix/povconfig -I../../vfe -isystem
> /usr/include/qt5 -isystem /usr/include/qt5/QtCore -I.
> -I/usr/lib64/qt5/mkspecs/linux-g++ -o
> tmp/QTP/qtpovray-3.80.1/source/base/image/openexr.o
> ...../../source/base/image/openexr.cpp
> In file included from ../../source/base/image/openexr.cpp:49:0:
> /usr/include/OpenEXR/ImfRgbaFile.h:50:23: fatal error: ImfHeader.h: No such file
> or directory
> #include <ImfHeader.h>
> ^
> compilation terminated.
> make[1]: *** [tmp/QTP/qtpovray-3.80.1/source/base/image/openexr.o] Error 1
> make[1]: Leaving directory `/tmp/QTP/qtpovray-3.80.1/qt/libpovray'
> make: *** [sub-qt-libpovray-make_first-ordered] Error 2
>
> still needs adding the 'INCLUDEPATH += "/usr/include/OpenEXR"' line to the
> 'libpovray.pro' file to make it work. not to worry though, it is easy to patch
> from the (unwritten as yet :-)) qtpovray.SlackBuild script.
Or, Slackware could update to a post-Ming Dynasty copy of OpenEXR which
correctly uses
#include "ImfHeader.h"
:)
I do want to make a note somewhere of how to work around Neolithic
OpenEXR...
Or, the customer is always right and I'll figure out how to make a
qtpovray.SlackBuild. In all my years of Slackware, I never did that. I
always just downloaded source and built.
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
dick balaska <dic### [at] buckosoftcom> wrote:
> On 07/21/2018 09:36 AM, jr wrote:
> >> It is also rumored to build and run on Slackware 14.1
> > "out of the box", no.
> > still needs adding the 'INCLUDEPATH += "/usr/include/OpenEXR"' line to the
> > 'libpovray.pro' file to make it work. not to worry though, it is easy to patch
> > from the (unwritten as yet :-)) qtpovray.SlackBuild script.
>
> Or, Slackware could update to a post-Ming Dynasty copy of OpenEXR which
> correctly uses
> #include "ImfHeader.h"
>
> :)
>
> I do want to make a note somewhere of how to work around Neolithic
> OpenEXR...
Slackware users recommend clay tablet(s) + stylus. ;-)
> Or, the customer is always right and I'll figure out how to make a
> qtpovray.SlackBuild. In all my years of Slackware, I never did that. I
> always just downloaded source and built.
you could. or, providing you don't mind deviation from Slackware "policy" to
install under '/usr/', I can post one in a day or two (rigged to install under
'/usr/local/' where all my povray stuff goes).
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
"jr" <cre### [at] gmailcom> wrote:
> dick balaska <dic### [at] buckosoftcom> wrote:
> > Or, the customer is always right and I'll figure out how to make a
> > qtpovray.SlackBuild. In all my years of Slackware, I never did that. I
> > always just downloaded source and built.
>
> you could. or, providing you don't mind deviation from Slackware "policy" to
> install under '/usr/', I can post one in a day or two (rigged to install under
> '/usr/local/' where all my povray stuff goes).
on second thoughts, perhaps you *should* write the package script. I just found
out that your 'Makefile's do not honour the 'DESTDIR' variable. ouch. have fun..
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Well, I've played around with this, and it is of course different - but I think
that even after giving it some time to get past the adjustment phase, I find
certain things a bit awkward.
The right-click to "select for rendering" is a real mistake waiting to happen -
I think most folks are used to rendering the scene in the selected tab, and even
if this was the original default POV-Ray, I think that would be the intuitively
expected behaviour.
I currently have a scene NOT in the /home/oem/documents directory that I'd like
to edit and render. It's not at all clear how to do that.
The use of the screen real estate doesn't seem conducive to writing scenes - at
least for me. I don't really need to see the file directory the whole time, nor
even the message pane. Though having the option to put the message pane as a
vertical strip where the file directory currently is would be nice I think.
Vertically stacking the scene tabs rather than trying to cram them on screen
horizontally would be the best way to arrange them I think - even with the
official distribution (I know, it's a Windows editor...)
Adding some additional color options would be great, or at least having the full
range of available coloring in the usual Win editor - colored numerical values,
x, y, z, vectors, and other reserved keywords.
The docking behaviour of the render window took a bit of time to grapple with.
I mistakenly docked it above the coding tabs and it was pretty challenging to
get it resized and put back into the default position. It's also "always on
top" which I think should be an option that can be toggled.
The resource filter thing is also a bit confusing. It seems to do the opposite
of what the description implies ... but that could just be me.
Clicking the "NEW" button/icon tries to open something "under" the currently
selected filename instead of "in" the current directory.
"Insert" button/icon currently does nothing that I can see.
I do very much like the line numbering - that's much better than just showing
what line the cursor is currently on.
I also like the option to put some of the comments and keywords in BOLD text.
Thanks for getting this all set up and running :) I'm happy to have started
the switch from M$, and look forward to (re)learning some of the pre- and
post-render commands that can be used, and other helpful tools as well.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/29/2018 02:09 PM, Bald Eagle wrote:
Thank you for the feedback.
> Well, I've played around with this, and it is of course different - but I think
> that even after giving it some time to get past the adjustment phase, I find
> certain things a bit awkward.
>
> The right-click to "select for rendering" is a real mistake waiting to happen -
> I think most folks are used to rendering the scene in the selected tab, and even
> if this was the original default POV-Ray, I think that would be the intuitively
> expected behaviour.
I can change it to a "soft default". If no file is "select for
rendering", then use the current displayed file. I've actually caught
myself doing this with the multiple virgin virtual machines I've been
running. (open a file, click render, um what? oh yeah...)
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=4
(My next band is going to be called Virgin Virtual Machines)
>
> I currently have a scene NOT in the /home/oem/documents directory that I'd like
> to edit and render. It's not at all clear how to do that.
Currently, you can create another workspace, which is probably not what
you want to do.
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=5
>
> The use of the screen real estate doesn't seem conducive to writing scenes - at
> least for me. I don't really need to see the file directory the whole time, nor
> even the message pane. Though having the option to put the message pane as a
> vertical strip where the file directory currently is would be nice I think.
You can do that now.
http://www.buckosoft.com/qtpovray/g/qtpovrayVerticalConsole.png
>
> Vertically stacking the scene tabs rather than trying to cram them on screen
> horizontally would be the best way to arrange them I think - even with the
> official distribution (I know, it's a Windows editor...)
The file list gives you a vertical list of the files, if you had some
organization. It sounds like you're scatterbrained. ;)
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=6
>
> Adding some additional color options would be great, or at least having the full
> range of available coloring in the usual Win editor - colored numerical values,
> x, y, z, vectors, and other reserved keywords.
I agree. I always wanted to revisit that. I miss having a red "=+"
>
> The docking behaviour of the render window took a bit of time to grapple with.
> I mistakenly docked it above the coding tabs and it was pretty challenging to
> get it resized and put back into the default position.
That's a feature of the Qt toolkit. I agree it can be tedious. I've
wished I could blame it on my slow PC not keeping up, but my PC isn't
slow. I like to move the render window to my other monitor, which is
far, and that is tedious too. (If the mouse gets ahead of the window, it
loses it.)
> It's also "always on
> top" which I think should be an option that can be toggled.
I *may* be able to do something about that.
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=7
>
> The resource filter thing is also a bit confusing. It seems to do the opposite
> of what the description implies ... but that could just be me.
Hmm, I'll re-read the doc. qtpovray is modeled on eclipse, which uses
an *exclude* filter system. I prefer that to Qt's built in filter
system which is an *include* model.
>
> Clicking the "NEW" button/icon tries to open something "under" the currently
> selected filename instead of "in" the current directory.
I'll look at this further.
>
> "Insert" button/icon currently does nothing that I can see.
If you open the configure dialog, are the checkmarks all green?
http://www.buckosoft.com/qtpovray/configDirs.html
and
http://www.buckosoft.com/qtpovray/g/qtpovPreferencesSystem.png
Did you install qtpovray-extras?
>
> I do very much like the line numbering - that's much better than just showing
> what line the cursor is currently on.
>
> I also like the option to put some of the comments and keywords in BOLD text.
>
>
>
> Thanks for getting this all set up and running :) I'm happy to have started
> the switch from M$, and look forward to (re)learning some of the pre- and
> post-render commands that can be used, and other helpful tools as well.
Do you want to do post-render shellouts? I don't support that (yet).
It might just work, but I never do that. I at least have to test it.
http://www.buckosoft.com/qtpovray/bugzilla/show_bug.cgi?id=8
Thanks again for being a valued customer. :)
--
dik
Rendered 328976 of 330000 (99%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hello,
I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
After my first test using "optics.pov" i got this parse error from the povray's
output:
"Parse Error: Macros require #version 3.1 or later but #version 3.00 is set.
at File: colors.inc Line: 167 Col: 2"
Very rare message. The colors.inc file is standard; i have not touched in any way. I
don't know how to fix this because the #version directive was not modified at all.
--
hugo giulietti <hug### [at] gmailcom>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 31.07.2018 um 12:03 schrieb hugo giulietti:
> Hello,
>
> I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
> After my first test using "optics.pov" i got this parse error from the povray's
output:
>
> "Parse Error: Macros require #version 3.1 or later but #version 3.00 is set.
> at File: colors.inc Line: 167 Col: 2"
>
> Very rare message. The colors.inc file is standard; i have not touched in any way. I
don't know how to fix this because the #version directive was not modified at all.
>
That's seriously odd. Please verify that line 13 of `colors.inc` reads
`#version 3.5;`
If that's not the case, for some obscure reason you have a far outdated
version of the file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 07/31/2018 07:32 AM, clipka wrote:
> Am 31.07.2018 um 12:03 schrieb hugo giulietti:
>> Hello,
>>
>> I installed qtpovray in my lubuntu 16.04 using the ppa for automatic updates.
...
>>
>
> That's seriously odd. Please verify that line 13 of `colors.inc` reads
> `#version 3.5;`
>
> If that's not the case, for some obscure reason you have a far outdated
> version of the file.
>
Also check the environment variable POVINI is not pointing at an old
povray.ini file which might itself be pointing to old include libraries.
'echo $POVINI' in an xterm window to check.
Bill P.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
It reads #version 3.5
xD I installed qtpovray just 2-3 hours ago! It's updated! (i hope so...)
I have not modified anything. Just run a test and the error comes up into the command
output.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
