[Bf-committers] Blender event pipeline

[Joseph Paavola]

Thanks for the clarification Knapp. I'm sorry it took so long to get back to you but I had no internet access the last few days. This sounds like it could save a lot of my time. I'll definitely be looking into this.  

Dr. Who?

> On Jun 9, 2015, at 2:42 PM, Knapp <magick.crow at gmail.com> wrote:
> 
> The undo history collects each thing that the user does so it can store it
> for the undo history. I was thinking that it would basically collect the
> same info as the info you wanted to collect. To be clear I am nothing but a
> beginner here which is why I posted it as a question.
> 
>> On Tue, Jun 9, 2015 at 5:24 PM, Joseph Paavola <joepaavola at gmail.com> wrote:
>> 
>> I'm sorry but I'm not sure I follow Knapp.
>> 
>> Dr. Who?
>> 
>>> On Jun 9, 2015, at 1:12 AM, Knapp <magick.crow at gmail.com> wrote:
>>> 
>>> Would that not be a lot like the undo logger?
>>> 
>>> On Tue, Jun 9, 2015 at 5:22 AM, Campbell Barton <ideasman42 at gmail.com>
>>> wrote:
>>> 
>>>> On Tue, Jun 9, 2015 at 12:17 PM, Joseph Paavola <joepaavola at gmail.com>
>>>> wrote:
>>>>> Dear Blender Enthusiasts:
>>>>> I'm really excited to contribute to the blender source code! Me and my
>>>>> compatriot have made tentative steps into the blender source, making
>>>> simple
>>>>> changes to the compositor nodes and certain operators.
>>>>> 
>>>>> We're are trying to achieve a setup where one blender application will
>>>>> mirror another for experiential purposes. As a first step, we're
>> looking
>>>> to
>>>>> find the exact location of the portion of code that is called whenever
>>>> the
>>>>> user makes a change to the file. Our code would be called whenever the
>>>> user
>>>>> changes properties, moves objects, modifies meshes, etc. We've seen
>> this
>>>>> behavior before in the log located in the info panel but have yet to
>>>> find a
>>>>> way to get that information.
>>>>> 
>>>>> Once we get that information, we will send it to the other blender
>>>> client,
>>>>> where the same functions will be called in the same order. This will
>>>> ensure
>>>>> that both clients will have the same scene at any given time.
>>>>> 
>>>>> Where exactly in the source should we add function calls to achieve the
>>>>> desired behavior?
>>>> 
>>>> Hi Joseph,
>>>> Check on ghost_event_proc and wm_event_add_ghostevent in
>>>> 
>>>> 
>> https://developer.blender.org/diffusion/B/browse/master/source/blender/windowmanager/intern/wm_window.c
>>>> These get the events from ghost.
>>>> 
>>>> wm_window_process_events may also be worth looking into (tells ghost
>>>> to process events)
>>>> 
>>>>> Thanks in advance for your time,
>>>>> Dr. Who?
>>>>> _______________________________________________
>>>>> Bf-committers mailing list
>>>>> Bf-committers at blender.org
>>>>> http://lists.blender.org/mailman/listinfo/bf-committers
>>>> 
>>>> 
>>>> 
>>>> --
>>>> - Campbell
>>>> _______________________________________________
>>>> Bf-committers mailing list
>>>> Bf-committers at blender.org
>>>> http://lists.blender.org/mailman/listinfo/bf-committers
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> Douglas E Knapp
>>> 
>>> Massage in Gelsenkirchen-Buer:
>>> http://douglas.bespin.org/tcm/ztab1.htm
>>> Please link to me and trade links with me!
>>> 
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>> 
> 
> 
> 
> -- 
> Douglas E Knapp
> 
> Massage in Gelsenkirchen-Buer:
> http://douglas.bespin.org/tcm/ztab1.htm
> Please link to me and trade links with me!
>