[Bf-committers] Feature Proposal

[Ton Roosendaal]

Hi,

> I've always thought that since the mouse is itself a 2D device, making
> it operate in three dimensions all at once is a strange task.  Thus, I
> like how in other programs the two mouse axes are mapped to (generally)
> viewport x and z, while another button activates movement around the y
> axis

There are a couple of original design concepts in Blender I still  
consider useful and very much worth sticking to. One of these ideas is  
to make 3d editing available without bothering with decisions what the  
X or Y or Z axis is.
The feature you describe is being dropped by other software (slowly)  
too. Only CAD programs keep sticking to it.

-Ton-



> ;It would be easy to implement (seeing as there's
> already a dropdown bar in the system settings for choosing mouse
> rotation behavior).  I'd suggest using some sort of key combination to
> switch between the two main axes and the third one, since the middle
> mouse button is used for a host of other things.
>
> But yeah, when the camera pitches in 3D view when all I wanted was to
> rotate it along a flat plane, it always irks me.
>
> - Charles
>
>
> --- Chris Burt <desoto@blender.spaceisbig.com> wrote:
>
>> I think advanced loop subdivide and the viewport behaviors are good
>> ideas.  The first feature however can be done simply by pressing CTRL
>> +
>> R multiple times so I'm afraid you'll have a difficult time
>> convincing
>> developers of the usefulness.  However, constraining rotation of the
>> viewport to certain axis would very nice in my opinion.  Especially
>> since grab and adding new objects uses the viewport for the objects
>> coordinates.  You have my thumbs up on that. (Whatever that means)
>>
>> Jonathan Merritt wrote:
>>
>>> Hello Bart,
>>>
>>>> After i talked with other cg artists about blender (i use Blender,
>> they
>>>> use 3dsMax) i started creating a feature proposal:
>>>> http://www.neeneenee.de/blender/features/
>>>
>>>
>>>
>>> I'd say that the first three of these features - advanced loop
>>> subdivide, hilight move axis, and the different viewport behaviours
>> -
>>> are all relatively minor things (certainly the last two).  However,
>>
>>> the relatively insignificant details of tiny features like these
>> seem
>>> to be endlessly, endlessly debated, so I can only wish you luck on
>>> finding a consensus... >:-]
>>>
>>> In Tuhopuu at least, the axis along which an object is being
>> dragged
>>> is already shown (as you describe) when that axis has been
>>> constrained.  I haven't been using the main Blender tree for a
>> while.
>>> Is that feature not yet available?
>>>
>>> Your final suggestion - a solidify function - sounds partially like
>>
>>> the "Cap Holes" modifier from 3DSMax.  I'm not sure exactly what
>> you
>>> mean by the dragging capability of this function though.  Could you
>>
>>> perhaps expand on that idea a little, maybe with some more
>> examples?
>>> What is the proposed algorithm, and (how) will it work for
>> complicated
>>> meshes?
>>>
>>> Jonathan Merritt.
>>> _______________________________________________
>>> Bf-committers mailing list
>>> Bf-committers@blender.org
>>> http://www.blender.org/mailman/listinfo/bf-committers
>>>
>>>
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers@blender.org
>> http://www.blender.org/mailman/listinfo/bf-committers
>>
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers@blender.org
> http://www.blender.org/mailman/listinfo/bf-committers
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton@blender.org  
http://www.blender.org