[Bf-committers] Modification Stack

[Austin Benesh]

You are correct. The method I'm developing captures the current EditMesh
every time free_editMesh is called or when the user calls to push it on the
stack. It then stores this on the "modification stack" (construction history
stack) for future calls. The method I'm creating may use more RAM, however,
seeing as how it stores an exact duplicate of the EditMesh on the stack. The
reason I do this is so no dependencies between stack levels are created, and
when a position in the stack is expelled there will not be need for massive
stack reconstruction. This same method can also be applied to certain other
things (such as NURBS, IPOs, etc.) If you have anything to expound on this
concept, I'd be glad to hear it.

-----Original Message-----
From: bf-committers-bounces at projects.blender.org
[mailto:bf-committers-bounces at projects.blender.org] On Behalf Of Ton
Roosendaal
Sent: Wednesday, February 09, 2005 4:34 AM
To: bf-blender developers
Subject: Re: [Bf-committers] Modification Stack

Hi,

The "modifier stack" is a confusing name. You can have non-destructive  
modifiers (in Blender too) which are now available as 'modifiers' in  
the code as well. Examples are Wave effect, Hook deform, and  
curve/lattice/armature deforms.

What 3ds and Maya offer are "construction history stacks", which is  
very much different. Blender's undo system nor event system currently  
supports that.

-Ton-


On 9 Feb, 2005, at 5:07, joeedh wrote:

> Austin Benesh wrote:
>
>> I have found a simple (and somewhat crude at the moment) way of  
>> storing the
>> EditMesh data in a stack after every time free_editMesh is called  
>> (only when
>> leaving edit mode, however). This data, through a simple drop-down  
>> menu, can
>> then be re-applied by simply replacing it with the current EditMesh.  
>> No
>> stack dependencies are created this way, but large amounts of RAM  
>> would be
>> used, dependent on how many EditMeshes you have in the stack. What I  
>> might
>> do is set a limit (a.k.a, 100), or make it user-controlled. Anyway,  
>> this
>> seems to be the best way to make a modifier stack. If you need more
>> clarification, please reply.
>>
> The best way would probably be to store undo meshes in the stack.   
> Remember, on each undo push the editmesh is converted into a special  
> compressed undo mesh.
>
> joeedh
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton at blender.org  
http://www.blender.org

_______________________________________________
Bf-committers mailing list
Bf-committers at projects.blender.org
http://projects.blender.org/mailman/listinfo/bf-committers