🚀 go-pugleaf

OK. Thanks to the guys at Acorn who helped me out with the Iconise protocol
messages. I have just one question:

Is pinboard broken, or am I doing something wrong? (It's hard to tell because
the instructions for Message_WindowInfo are so unhelpful and vague)

I appeal to the techpubs people at Acorn to *please* rewrite the page about
iconisation: It is *very* difficult to understand (especially the implied
context switches between iconiser and client)

I have coded the folowing:
On receipt of Messge_WindowInfo, I call Wimp_Poll once to allow the Un-Acked
message to get back to Pinboard, thus getting the iconisation to occur. I
then send (Wimp_SendMessage,17) a msg_WindowInfo to pinboard, thus getting
the correct icon and title.

In my attempts to get this working, I have tried *every* combination of
message types, acks, etc., and *only* the above seems to work (if I ack,
the machine locks up, most of the rest of the time, I get a blank title and
the "ic_?" sprite...)
The half-way point (without the Wimp_Poll in the middle) is when the title
text is correct, and for about 1/10th of a second, the icon is correct, and
then the icon is replaced by "ic_?".

Arrrgh!

So, anyway, I had it working, by using a Wimp_Poll... And then I reset my
machine and started it up without my normal boot sequence (i.e. a "blank"
RISC OS 3.10 A5000). Hey, presto! It's BROKEN again!
It works fine if I boot from my hard drive...

Arrrrgh! Why?

Has anybody ever actually tested pinboard with an application that supplies
sprite names *other* than the same name as the application's taskname?
(i.e. taskname = "edit", icon = "ic_edit"; taskname = "dsedit ii", icon =
"dsed-1" or "dsed-2" or "dsed-t"?)

Help! I'm at my wits end over what must qualify as the simplest message
protocol available! Arrrgh!
-- 
_________________  "I'd like to answer this question in two ways:
  /____ _ _/_ __       First in my normal voice, and then
 // / //_//_ /_/       in a silly, high-pitched whine." (Monty Python)