Pretty Hourglass

I just noticed on RO 4.03 there is a pretty hourglass that appears on boot.
It would be nice to get prettier hourglass functionality in RO 5.2x by default.
I seem to remember there were a few modules back in the “good old days” that replaced the standard hourglass module.
I appreciate as far as priorities go this isn’t high up, but the standard hourglass does look rather dated.

One of the things on the GraphicsV todo list is to add support for larger cursor images, for use in 180 DPI modes (‘EX0 EY0’). As part of that work I was also thinking of adding support for true-colour, alpha-blended cursor images – which I think everything post-RiscPC is able to support (although I’m not sure offhand if the Iyonix will do alpha blending). So once that’s implemented you should be able to use pretty much whatever you want for a cursor or hourglass image – for better or worse ;-)

I particularly liked the watch ‘Hourglass’ that came with NewerLook.
It’s like a wrist-watch when in enabled.
I still use it on my Risc PC.

On my Pi I’m using many pointer icons (from NewerLook and elsewhere), the Wimp Palette (so my mount pointer is white/black, not blue) and 32-bitted AddSprites.

It’s just the Hourglass module/look that needs upgrading :)

I just noticed on RO 4.03 there is a pretty hourglass that appears on boot.
It would be nice to get prettier hourglass functionality in RO 5.2x by default.

On the off chance, I did some digging in the RISC OS source code.
There appears to be an hourmake program with the same/similar images as used in RISC OS 4.

I’ll see what I can make of it given half a chance!

Take a look at this:
http://www.philipnet.co.uk/files/riscos/Hourglass.zip

This is made from the sprites in the RISC OS source code – which is different to the hourglass data that’s encoded into the Hourglass module source code.

The lines are curved (rather than straight). It’s not exactly the same as the RISC OS 4 Hourglass module but it’s close.

There is (almost) everything in the archive that’s needed to rebuild the module with new sprite data. The Hourglass sprites are included, which is the first step in improving them (if you want to).

I’ve just discovered a typo in the module source code (my doing) which made the Hourglass look slightly odd near the top.

I’ve corrected that, double checked the module and uploaded a new copy to the URL above :) .

There is (almost) everything in the archive that’s needed to rebuild the module with new sprite data. The Hourglass sprites are included, which is the first step in improving them (if you want to).

It’s sort of fortunate it isn’t all there – or I’d have to stop using my normal reply at work.

Director: “you need to make time”

Me: “I can’t get the parts. I’ve put in a req. but they are on back order”

Well, if you want to build it, you’re better off downloading the ROOL source code, setting up !Builder and letting it build the whole of RISC OS.
Then you’ll have everything you need to rebuild the module with new sprite data (and more!)

The one you built does look nicer with its curved edges and better ‘sand’ falling.

But if the LEDs are used, the top one is seems hardly visible to me (a long thin line across the top), and the bottom one seems invisible! Or is it just me?

It may not be coincidence that the LED displays are not tried in the test program!

But if the LEDs are used, the top one is seems hardly visible to me (a long thin line across the top), and the bottom one seems invisible! Or is it just me?
It may not be coincidence that the LED displays are not tried in the test program!

It’s not you! ;)
I did think about putting LED tests into the test program, but I wasn’t happy with the LEDs in the module and I wanted to work on that first.

That is awesome! Thanks!

While we’re on the subject of pointers, is there any chance that one of you knowledgeable types could possibly consider chiming in on the related Wikipedia talk page? (I’m well out of my depth, as ever.)

I won’t participate on the wiki as this is hearsay more than verifiable…
Anyway, there are two primary methods of displaying the pointer.

The first method, used by the likes of GEM and early Windows is to plot a pointer into the framebuffer, with various tricks to speed up the redraw. This can be determined by asking the machine to do something difficult, move the mouse rapidly, see if the pointer keeps up. Windows 3.1, are you listening?
The alternative method is to have the hardware plot the pointer directly into the screen display, akin to how some 8 bit micros used to plot the cursor. This is how the VIDC did it and has the amusing side effect is that the pointer still works during a system crash.