Re: [ff-cvs] journals mudyc tjl

[Tuomas Lukka]

On Tue, Aug 26, 2003 at 04:03:18AM +0300, Matti Katila wrote:
> On Sun, 24 Aug 2003, Tuomas J. Lukka wrote:
> > Log message:
> >     more
> > 
> > Patches:
> > Index: journals/mudyc
> > diff -u journals/mudyc:1.101 journals/mudyc:1.102
> > --- journals/mudyc:1.101    Sat Aug 23 06:11:35 2003
> > +++ journals/mudyc  Sun Aug 24 11:37:35 2003
> > @@ -85,7 +85,30 @@
> > +- [tjl] clean SelectListVob :
> 
> I only remembered this part on my bus trip but I used now Placeable object 
> on list items. First idea on my mind comes from here that we can then use
> LocalizationFunction to do the localization and place images etc. on list 
> (hmm, how about placing the selected part from pdf page in menu?). 

What is a localizationfunction?

> > +    Make a PEG with the following components:
> > +    1. make it immutable, so the constructor is called once with a suitable
> > +       array
> 
> done

Umm, the PEG? I would like to see a PEG *before* significant changes
from now on, as FenPDF is in **PRODUCTION USE**.

> > +    2. get index of node to be colorized from a coordinate system, 
> > +       in the OpenGL code, to allow
> > +       a "selection bar" to move when moving the mouse.
> 
> in libvob try vob/demo/mouse/mousemenu.py 
> Dragging does the selection bar trick but..  I don't really follow what 
> you mean.

Well, how does the selection bar work now? Recreating vobscenes?
Changing immutable vobs?

> > +       This needs a new vob type: SelectVob, which takes two or more 
> > coordinate systems:
> > +       it checks the value of the first one and calls a vob depending on 
> > that
> > +       to render, with the rest of the coordsyses as parameters.
> > +       - this is a primitive we need anyway at some point, to allow quick 
> > reaction
> > +         to mouse motions
> > +       - however, the primitive is only for temporary use - to obtain 
> > optimal
> > +         performance in the long run, the vobs themselves should check the 
> > cs
> > +         (or some other "activation thing").
> 
> I don't understand this part at all. How we get any events anyway, did 
> you turned them on from Os.cxx?

What events? I'm talking about a Vob that looks at a coordinate system
and decides, based on that, what to do. Nothing else. No events.
The event code then *USES* the SelectVob to do its bidding, without
having to change the VS.

> > +- [tjl] Think about what happens in the libvob & fenpdf event logic when 
> > the user
> > +  presses one button down, then another -- it's pretty fragile. How can we
> > +  make it work right in all cases?
> 
> Made it stole events. It works if you can give the right vobscene to it.

What steals which events?

        Tuomas