[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] wind_xget()



ons, 15,.12.2004 kl. 19.18 +0100, skrev Odd Skancke:
> ons, 15,.12.2004 kl. 19.04 +0100, skrev Odd Skancke:
> > > > Alrite.. lets vote, bit 9 is OK to indicate WF_FIRSTAREAXYWH
> > > >availability?
> > > >  
> > > >
> > > Ok for me, already integrate.
> > > 
> > 
> >  Whooopsie.. bit 9 is AGI_WF_WHEEL in the XaAES sources. I have no idea
> > what it is used for, or what it indicates. Let me investigate its
> > meaning :)
> 
>  Ok, AGI_WF_WHEEL indicates that
> wind_set(handle, WF_WHEEL, mode, whl_mode, 0, 0);
> is present and AGI_WF_FIRSTAREAXYWH indicates that
> wind_get(handle, WF_FIRSTAREAXYWH, clip_x, clip_y, clip_w, clip_h);
> is available.
> and AGI_WF_OPTS indicates that
> wind_set(handle, WF_OPTS, wopt0, wopt1, wopt2, wopt3);
> is available.
> 
> #define AGI_WF_WHEEL 0x0200
> #define AGI_WF_FIRSTAREAXYWH 0x0400
> #define AGI_WF_OPTS 0x0800
> 
> 
>  Is this OK everyone?
> 

 wopt3 in the quote above is ofcourse wrong :)

 I changed to;
wind_set(handle, WF_OPTS, mode, wopt0, wopt1, wopt2);
 and changed the options to 16-bit integers after a request by Arnaud.
Makes more sense this way. See newcalls.txt in the cvs source tree for
more details.

 Also added AGI_WM_REPOSED (value 0x400, bit 10 in out1) to
appl_getinfo(AES_MESSAGES(=12)) to indicate presence of WM_REPOSED(38).
Unsure if this is correct as you have to use wind_set(WF_OPTS) to make
the AES send it. Opinions?




> Regards,
> 
>  Odd Skancke
> 
> 
> 
>