Dennis you never replied on your preferences for this. I'll actually
be putting it in fairly soon
for the directfb/xserver/integrated wm project I'm doing.
Mike
On 5/21/06, Mike Emmel <[EMAIL PROTECTED]> wrote:
> To extend
>
> we could have
>
> SetState( IDirectFBWindowt *window, WindowState *state, int count );
>
> If count is -1 we read till hiting a null entry ?
>
> Or just must append with 0,0,0 ??
>
> Mike
>
>
> On 5/21/06, Mike Emmel <[EMAIL PROTECTED]> wrote:
> > On 5/21/06, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote:
> > > Mike Emmel wrote:
> > > > In working on the Xserver and finally starting on my own window
> > > > manager I found that it looks like it would be really useful to add a
> > > > SetVisible method to window this would allow the window manager to
> > > > hook setting the opacity so it could for example fade in and out the
> > > > window or perform some other transition like OSX does a 3D crumple. I
> > > > also noticed were missing minimize.
> > > >
> > > > So I propose we add
> > > >
> > > > SetVisible
> > > >
> > > > Not sure for minimize/maximize/fullscreen ?
> > > >
> > > >
> > > > maybe a SetWindowState ( mask )
> > > >
> > > > In fact we could simple add just SetWindowState that takes a mask it
> > > > would have
> > > >
> > > > NORMAL
> > > > MINIMIZED
> > > > MAXIMIZED
> > > >
> > > > HIDDEN
> > > > SHOWN
> > >
> > > These multiple choices shouldn't be in a mask or even in one.
> > > They're two enums. It would become awkward to change one item.
> > > You also have to ensure only one flag is set in each group.
> > >
> > > > And probably more but if we add the SetWindowState function with a mask
> > > > we can
> > > > add more as needed.
> > >
> > > Instead of one mask we should provide an array of attributes
> > > which can be ints, enums or whatever. Still one single function
> > > to set an attribute identified by its id (index).
> > >
> > > Attributes could be introduced at runtime, maybe by the wm.
> > >
> >
> > Okay thats fine we have a similar concept already for window creation
> > DFBWindowDescription
> >
> > But I think it should be a extensible interface as you said there are
> > a number of ways to code it up. Generally you would like name,type,
> > value triples.
> >
> > Any suggestions I don't like vararg functions myself since there hard
> > to wrap from other languages I don't mind have them for C but the core
> > function should take so sort of list of values. Also it should be easy
> > to do the trivial settings so it's not a paint to call.
> >
> > I'd suggest in
> >
> > struct WindowState {
> > char *name;
> > enum PrimitiveType { Pointer,Int,Short,String .... etc } type;
> > union value {
> > void *ptrval
> > int intval
> > long long lval
> > ....
> > etc
> > }
> >
> > }
> >
> >
> > SetState( IDirectFBWindow *window, WindowState *state);
> >
> > ???
> >
> > A generic name,type,value triple is generally useful actually.
> >
> > Mike
> >
> >
> >
> > > --
> > > Best regards,
> > > Denis Oliver Kropp
> > >
> > > .------------------------------------------.
> > > | DirectFB - Hardware accelerated graphics |
> > > | http://www.directfb.org/ |
> > > "------------------------------------------"
> > >
> >
>
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
