GitLab

Deleted RISC OS 2 support. Use defines from OS_Byte and OS_Word headers.
Tested in a ROM build, help and syntax looked OK.

Version 2.18. Tagged as 'Hourglass-2_18'

Version 2.17. Tagged as 'Hourglass-2_17'

Detail:
  In Ursula, functionality was added such that if anyone else changes the
  pointer colours (except via SWI Hourglass_Colours) then the Hourglass module
  remembered the change, and re-applied it when the hourglass was turned off.
  The problem was that it determines that the colours have been changed by
  reading the colours in use at each animation stage, and comparing them with
  those that it programmed most recently. We got away with this in the final
  Ursula version (and in a branched version, derived thereof) because the
  hourglass used unusual colours; however, we've picked up an intermediate
  version that still has a RISC OS 3 style hourglass, with pointer colour 1
  being full intensity cyan - /the same as the default Wimp pointer colour 1/.
  This means that the hourglass ignored the Wimp's initial programming of
  pointer colour 1, and restored it to black at the end of the boot sequence.
  The solution I have used is to install a routine on PaletteV, and note
  the pointer colours being programmed (either singly or in bulk) directly.
Admin:
  Tested on Tungsten.

Version 2.16. Tagged as 'Hourglass-2_16'

Currently the help text is not internationalised :-(

Version 2.15. Tagged as 'Hourglass-2_15'

Version 2.14. Tagged as 'Hourglass-2_14'

  Updated to build using objasm instead of aasm.
  Sources changed to be objasm-compatible.
Admin:
  Requires Library 0.72 or later.
  Requires BuildSys 3.09 or later.
  Requires Env 0.65 or later.

Version 2.13. Tagged as 'Hourglass-2_13'

* Killing the module before it had shown the hourglass used to remove the
  pointer.
* If an hourglass with a long lead-in time is pending, and a (shorter lead-in)
  second hourglass is started, the time that the animation actually starts is
  now determined by the sooner of the two, rather than always by the top-level
  hourglass' lead-in time.
* If something else changes the pointer number or colours while the Hourglass
  is animating, the new values are remembered and put into effect when the
  hourglass stops, overriding those that were active when the hourglass started.
* Under certain circumstances, R10 could be corrupted on exit, leading to
  data aborts being generated by the Wimp error box code. Fixing this also
  means that Hourglass_Smash can call Hourglass_Off directly, rather than
  having to issue Hourglass_Off as a SWI.

Bugfix: new hourglass colours are marked as pending until they are implemented (at the next animation frame), so if the hourglass is turned all the way off before then, the module can correctly determine which pointer colours need redefining to correctly display the standard pointer.