As painful as this attitude seems, I'd have to agree with it. The
idea here is to modify expectations -- mostly on the developers part.
Umgiven that the next number is to be 6.0 I wouldn't mind seeing
that "200 bugs" turn into "0 bugs" in the near future rather than have
to learn new UI. It'
This seems like the basis of a religious war...like endianness.
Even though I generally like to do things the way mathematicians do it,
I'd suggest leaving it the Blender traditional way by default and invite
anyone who strongly prefers it the other way to write an API function
to switch the sense
Then h on unhidden to hide single, h on hidden to unhide single, and
Alt+h to unhide all (or hide all?). No doubt that
using a character as a toggle is convenient whenever there is an on-off choice.
On Sat, Jul 23, 2011 at 11:42 AM, Jonathan Williamson
wrote:
> I have to agree with Daniel. I con
The change being complained about below is clearly to fit someone's
notion of elegance, not functionality. As such, it wasn't a necessary
changeand in my option it wasn't even a good change.
If you don't supply a predictable API people will look elsewhere. It might
take time before some othe
I have to agree with this completely. If the API contract is not
maintained then
the API is not worth learning. Having the API change without necessary
reason after I've relied upon it to make something and sent it out the door
makes the product unusable. It is better not to try and to make thin
I've a 2.49 script I've been wondering when I should try updating to
2.5x, and I see now that the answer is NEVER.
That's ok. I've found the documentation for the new scheme, and
possibly the new scheme itself -- though that is unclear -- almost
impenetrable. Sticking with 2.49 might be the be b
er at
> remembering positions of icons than random letters on a keyboard. I think I
> can guess T, but what does N even stand for!? For Non-English, or English as
> a second language users I reckon this would be even harder, because they
> would have a harder time guessing what T stood fo
t; just find a way to have it sit there at the top/bottom of the tools
>> nicely.
>> >
>> > cheers,
>> > mario
>> >
>> >
>> > On Mon, Jun 13, 2011 at 6:19 AM, Jonathan Smith
>> wrote:
>> >> You are probably right, us
I'd agree. Find ways to use less real estate, not more.
On Sun, Jun 12, 2011 at 9:04 AM, Aurel W. wrote:
> Hi,
>
> I think that this would be rather unpractical, it takes way to much
> visual space for what it represents. If i want to collapse those
> panels, i want them gone, not taking a lot o
http://www.wikivs.com/wiki/Git_vs_Mercurial
Other than not particularly liking SVN I've no personal preference, but
it looks like Mercurial would be a better match for Blender -- both in
terms of a Python orientation and Windows support.
On Thu, May 26, 2011 at 5:25 PM, Tom M wrote:
> It was di
I'm not inclined to see Maya et. al. as THE MARKET. I think
the 3D virtual reality environments are probably already a larger
market for Blender, if a currently largely invisible one.
Certainly, if Blender is to ever have a really huge user base
it will be in the Metaverse. This is the place whe
Yank (ctrl-y) is an extremely old keyboard standard. TECO was using
it in the early 70s. Blender has enough trouble with an out-of-step UI
already without removing one point where it is in line with normal
software. I think if it has to be one or the other then it should be what
the rest of the
Why not on collision try calling each object's on_collision method if
it exists, and handle events like every other modern system? I thought
there was some way in python of getting an object's methods.
I'd suggest looking for on_collision_start, and on_collision_continuing
methods to call.
(
13 matches
Mail list logo