On 16.12.2013 07:57, Thomas Dinges wrote:
Microsoft itself drops support for it in April already.
If someone steps up and will support XP, I am fine with this. But I am not
going to waste time with it.
Code wise and library wise it’s just a pain to support such a big variety of
OS, and we
I believe Asbjorn is willing to support and maintain Blender for Win XP.
I'm not a developer actually, but if I was, I wouldn't also Waste Time on
Xp as Thomas said.
I don't care the market share and who uses it. The maker of it says they
don't even like it again, how much more myself.
If
On 16.12.2013 11:59, Nkansah Rexford wrote:
I believe Asbjorn is willing to support and maintain Blender for Win XP.
Heh, absolutely not.
But if Blender 2.69 works on XP today, there's no reason why it should
stop working April next year, just because Microsoft doesn't officially
support XP
On 16 November 2013 21:36, Mike Pan mike.c@gmail.com wrote:
Thus, if possible, I'd suggest waiting for 3.3.3 or at least use 3.3.3RC2
which has the OS X issue fixed: http://python.org/download/releases/3.3.3/
Jens upgraded the Python libs for OS X to 3.3.3; he said in IRC that
it works
Will update python on linux this week.
Just wondering, does it make sense to wait for 3.4 or it's not gonna to be
release until our 2.70?
On Mon, Dec 16, 2013 at 5:29 PM, Alex Fraser a...@phatcore.com wrote:
On 16 November 2013 21:36, Mike Pan mike.c@gmail.com wrote:
Thus, if possible,
On 16 December 2013 22:31, Sergey Sharybin sergey@gmail.com wrote:
Will update python on linux this week.
Awesome :-)
Just wondering, does it make sense to wait for 3.4 or it's not gonna to be
release until our 2.70?
3.4 is due out on the 23rd of February [1]. But since 3.3.0 apparently
Hmmh… Blender 2.70 is supposed to be released early in March, so py3.4
could make it… And it would be nice to get rid of that ugly Windows bug
(you know, unicode in win console) in 2.70. ;)
On 16/12/2013 12:45, Alex Fraser wrote:
On 16 December 2013 22:31, Sergey Sharybin sergey@gmail.com
Bastien, we couldn't use lib which was compiled a week before the release.
Not enough time to fully check it. Also, release schedules are tending to
delay, you know.
On Mon, Dec 16, 2013 at 7:29 PM, Bastien Montagne montagn...@wanadoo.frwrote:
Hmmh… Blender 2.70 is supposed to be released
Hello to all,
If we use inside the operator check the function BKE_report, it is not
displayed in the UI.
This is normal behavior or is it a bug?
Thank you,
ruesp83
___
Bf-committers mailing list
Bf-committers@blender.org
What is the operator check, can you be more precise and explain
exactly where you are putting BKE_report call?
On Mon, Dec 16, 2013 at 4:17 PM, Fabio Russo rues...@gmail.com wrote:
Hello to all,
If we use inside the operator check the function BKE_report, it is not
displayed in the UI.
This
I refer to such a situation: http://www.pasteall.org/48064/c
2013/12/16 Brecht Van Lommel brechtvanlom...@pandora.be
What is the operator check, can you be more precise and explain
exactly where you are putting BKE_report call?
On Mon, Dec 16, 2013 at 4:17 PM, Fabio Russo rues...@gmail.com
Ah, this seems to be a new callback. I think the current purpose with
the image save operator is to validate the settings before the users
actually does anything with the operator, it's to correct remembered
properties. So for that kind of purpose there should be no message, it
should just
Yep, check is to validate settings to avoid having to maintain a valid
state within draw callback for eg which is now disallowed since it
caused too many problems.
Its also used to ensure .blend extension is used when saving.
Don't think check() should be reporting back to the user, perhaps we
Upgraded Design + Theme Options for 3D Cursor I think would be an excellent
step forward. This might also land in the realm of the Widget upgrade
stuff.
-Sean
On Sat, Dec 14, 2013 at 11:56 AM, Antony Riakiotakis kal...@gmail.comwrote:
I reverted the commit a few minutes ago. For sculpting I
14 matches
Mail list logo
