DragASprite_Start

[Marco Baye]

Richard van der Hoff <richard at rvanderhoff.org.uk> wrote:

> Tony van der Hoff <tony at mk-net.demon.co.uk> wrote:

> > Marco Baye <Marco.Baye at tu-clausthal.de> wrote:

> > > [snip]
> > > Any chance of adding
> > > 
> > > #define dragasprite_SYSTEM_SPRITE_AREA (osspriteop_area const*) 0
> > > #define dragasprite_WIMP_SPRITE_AREA   (osspriteop_area const*) 1
> > > 
> > > to "oslib/dragasprite.h" ?
> > > 
> > [snip]
> > 
> > Yes, that seems a reasonable thing to do. I'll put it on the list. Thanks.
> > 
> 
> Hmm; I only have a rather old version of oslib to hand, but in it I have 
> 
> #define wimpspriteop_AREA  ((osspriteop_area *) 0x1u)
> 
> (that's in wimpspriteop.h), though I can't find one for the system sprite
> area.
> 
> Anyway, the point is, those constants aren't limited to use with
> dragasprite, as they apply to almost every sprite operation under the wimp,
> so dragasprite.h is the wrong place for them, IMHO.

True. I asked for them to be in dragasprite.h because of the
StrongHelp manual. The dragasprite_start StrongHelp page links to
osspriteop_area, but neither of those two pages links to the
wimpspriteop_AREA definition. Maybe it's possible to add this missing
link to the "Description" field of all operations that support these
constants?
Given the fact that the manual is created automatically, maybe
that's quite hard. Maybe not.

Another possibility would be to define two distinctly named
constants for every operation that supports the two values, but that
sounds rather messy...

Cu,

Marco Baye

-- 
ntalk://Marco@dionin.esw-heim.tu-clausthal.de
65816 Cross assembler    (RISC OS,DOS/Win,Unix/Linux,AmigaOS,OS/2)
ntalk, CBM drive access  (RISC OS)
Mouse driver, boot maker (C-128)
=> http://home.pages.de/~mac_bacon/ <=

... Reality is for people who can't handle Star Trek.