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