On Mon, Aug 6, 2012 at 5:10 AM, Paul Melis paul.me...@sara.nl wrote:
1) The search facility is very hard to use, and I find it unclear to see
what fields are actually searched. You can enter some terms, but it's
impossible (it seems) to search on, say, words in the title. This makes
is hard to
I would say if frameserver (in his current state) is still helpful for some
usages, let's
keep it as is for at least a while. If it's buggy / unstable/ unusable i
would rather either
completely remove it or at least IFDEF it.
Even if some tool could be useful for somebody, we should either
Some notes...
- frameserver can be disabled in cmake WITH_IMAGE_FRAMESERVER
- added frameserver to our image format docs, moved frameserver doc
into our manual.
http://wiki.blender.org/index.php/Doc:2.6/Manual/Render/Output#Image_Formats
Hi Sergey,
I would say if frameserver (in his current state) is still helpful for
some usages, let's keep it as is for at least a while. If it's buggy /
unstable/ unusable i would rather either completely remove it or at
least IFDEF it.
AFAIK, it works, currently.
Even if some tool could
Hi,
From: Peter Schlaile pe...@schlaile.de
To: bf-committers@blender.org
Sent: Monday, August 6, 2012 2:20:59 PM
Subject: Re: [Bf-committers] Remove Frameserver
And: as I mentioned, if someone finds time to write a python add-on
replacement,
please go
Hi, I agree that it shouldn't behave differently depending on the engine.
Probably storing the property per face is a bad decision, however I think
that changing images should somehow at least expose an option to do aspect
correction. This patch was written to address bug #31962
