Re: RISCOS_lib and alternatives

Thread View: comp.sys.acorn.tech

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Stephen Mansfield Thu, 28 Jan 1993 09:49

#815

Author: Stephen Mansfield
Date: Thu, 28 Jan 1993 09:49

35 lines
2237 bytes

In reply to Andrew Black & Ian Palmer:

I to think that the RISC OS Library is not worth bothering with.
But what I would like to know about is 'several poll loops' in one program.
I am, at this point, looking into this technique and am totally dismayed
at the lack of documentation on the topic as pointed out by Andrew with
respect to magazines and PRM's I might add!!!

Ian knocked the problem on the head with who's in control of what...the
programmer or the library...when the programmer is in control, the program is 
a lot easier to debug and design, also I'm currently looking at DeskLib and
evaluating its merits...it looks pretty goods so far. 

The real reason for this posting is to ask for help.  Could some kind person
briefly detail the use of several polling loops with respect to dialogue
boxes, whether connected to the menu tree or static.  I only realised about
a month ago that this is how the 'dbox' section of the RISC OS Library
works.  I have tried to duplicate this feature using the MENUDIE (0x400c9)
message of RISC OS 3 and have had partial success, but I feel if I ask
about this then perhaps a concise and clear way of doing this can be made
public...its almost a scandle that this is kept a secret.

Also, if there are other areas where they are of use in a program, perhaps
they could be given a mention too.

All help given would be WARMLY welcomed...

Also, of amusement...do you know how long it took me to find out that static
dbox's can be displayed using the 'Wimp_CreateMenu' call?  A loooonnnnggg time.
...its not documented in the pages of the PRM where you'd expect...NO...its in
the application notes at the BACK of volume III!!!  How many novice
programmers know this?


Stephen Mansfield.

Re: RISCOS_lib and alternatives

#798

Author: Stephen Burke
Date: Thu, 28 Jan 1993 18:45

20 lines
1743 bytes

In article <KERS.93Jan28131720@cdollin.hpl.hp.com>, kers@hplb.hpl.hp.com (Chris Dollin) writes:
> It's much easier to have but the one loop, and (if *necessary*) cut
> off some of the functionality while your oh-so-special box is up
> there. I agree that RISCOSLib can get in the way, but that's not a
> property of being the single polling loop; it's a property of being
> not terribly well designed. IMAO.

I think it depends on the problem. With a single polling loop you have to
have state flags for every possible state your program might be in. If some
of these states are very different from the "normal" state then it may make
sense to have separate polling loops for these. I don't think it's too
difficult to make sure that all the standard things are still taken care
of.

e----><----p | Stephen Burke           | Internet: burke@vxdesy.desy.de
 H   H   1   | Gruppe FH1T (Liverpool) | DECnet:   vxdesy::burke (13313::burke)
 H   H  11   | DESY, Notkestrasse 85   | BITNET:   BURKE@DESYVAX or SB2@UKACRL
 HHHHH   1   | 2000 Hamburg 52         | JANET:    sb2@uk.ac.rl.ib
 H   H   1   | Germany                 | Phone:    + 49 40 8998 2282
 H   H 11111 | HERA, the world's largest electron microscope!

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads