Wimp_SetIconState block
Tony van der Hoff
tony at mk-net.demon.co.uk
Wed Aug 28 14:58:00 BST 2002
On 25 Aug 2002, in message <e6168e6b4b.druck at druck.freeuk.net>,
David J. Ruck <druck at druck.org.uk> wrote:
> On 25 Aug 2002 Philip Ludlam <philip at philipnet.com> wrote:
> > Whilst programming with OSLib I discovered that OSLib didn't define a
> > block suitable for the Wimp_SetIconState SWI.
> >
> > I quickly whipped up:
> > typedef struct wimp_set_icon_state_block
> > { wimp_w w;
> > wimp_i i;
> > wimp_icon_flags eor_bits;
> > wimp_icon_flags clear_bits;
> > } wimp_set_icon_state_block;
> > and have been using it without a problem.
> >
> > Is there a reason why OSLib doesn't have a similar definition (does it
> > expect you to use the oslib call rather than set up a block and call the
> > SWI yourself) or is it just an omission?
>
> There is the wimp_set_icon_state(), but strangely instead of taking a block
> like the majority of other APIs, it takes 4 parameters saves them on to the
> stack and makes the SWI call. This is going to be less efficent where
> multiple calls are required, so please can we have block taking variant.
>
SWI Wimp_SetIconStateFromBlock and TYPE Wimp_SetIconStateBlock are now
defined.
Help_FullMessageRequest, Help_FullMessageReply, Help_FullMessageEnable are
now defined.
The changed files are available from CVS at SourceForge.
--
Tony van der Hoff | MailTo:tony at mk-net.demon.co.uk
| MailTo:avanderhoff at iee.org
Buckinghamshire, England | http:www.mk-net.demon.co.uk
More information about the oslib-user
mailing list