Boot into Dr. Wimp application

Hello,
Can I force Risc OS to boot into my program and show it on the screen
without an additional mouse click on the icon bar symbol?

Arno

Double click on !Boot to open the configuration window:

Click on Boot then Click on Run.

Then drag your application to Run at startup.

This will load your appliation to the iconbar.

Try putting a PROCwimp_openwindow somewhere in DEf PROCuser_initialise, after the window has been initialised. This is a semi educated guess.

Can I force Risc OS to boot into my program

See above for how to get RISC OS to boot it.

and show it on the screen without an additional mouse click on the icon bar symbol?

As it is your program, you’re in luck. Your Wimp_Poll handling will do stuff in return to a click on the iconbar icon. I don’t use Dr. Wimp so I can’t advise on specific function names. If it is like the library I use, it will call a function to deal with the iconbar click. Remember the function that is called.

Now go to the initialisation function. The one that initialises the wimp task, loads the windows, etc, etc. At the end of that, drop in a call to the function that is called upon mouse clicks on the icon bar. This ought to have the effect you are looking for.

That’s a bit of a mouthful, so hopefully it’ll make sense when looking at the code. ;-)

Thank you Kevin, thank you Rick,
I tried Kevin’s solution and had success, will do that with Rick’s suggestion later.
One more question, is there no possibility to start an application without access
to the source code?
Edit: …start the application and show the window, my Raspberry Pi is used as an
embedded system and no keyboard or mouse is connected.

It… Gets complicated. I guess, at a pinch, you could wait on the task started notification, try to work out which icon belong to the task, position the mouse there and fake a mouse click? All conjecture, for I’ve never needed to do such a thing. I can’t imagine it can’t be done, but I can imagine it wouldn’t exactly be straightforward.

Oooh, hang on a moment. How about wait for the task to start, get the task handle, and then set a post-poll filter to hijack one of the early messages (doesn’t the wimp probe the task to see if it can change memory slots or something like that at start-up?) and change it to a faked mouse click on the icon bar icon? At this point the filter would unregister itself and die.

I would say to hijack the first null poll, but that’ll only work if the task is not idling for a long time with null events disabled. Though… Having said that, couldn’t a pre-poll filter amend this behaviour as well?

Mmmmm, this is starting to sound interesting. ;-)

There is an app called !Highway by Bernard Veasey that
is long these lines. It is in BASIC so might be easy to modify to do what is required. I imagine feedback to the author would be good in the long run though.
Lots of other interesting stuff also at

http://www.bapfish.org.uk/soft.html

@Ronald:
!Highway has interesting features and the homepage from Bernard Veasey is very interesting too.
I know what I will do this weekend.
@Rick:
Ok Rick, I’ve got the message it’s not so easy to accomplish that task. :)

Can I force Risc OS to boot into my program and show it on the screen without an additional mouse click on the icon bar symbol?

As Rick says this is a bit tricky but you could try the following procedure:

Get the task handle of the application you’re interested in. Either by calling Wimp_StartTask to start it and noting the returned handle, or by using TaskManager_EnumerateTasks if it’s already running.

Use Wimp_GetWindowInfo on the iconbar to find the number of iconbar icons. Send an User Message Acknowledge (19) to each icon in turn to find the handle of the task owning that icon.

When the owner handle matches your task handle send a MouseClick event to that iconbar icon.

I’ve put a couple of applets demonstrating this here

send a MouseClick event to that iconbar icon.

Just looked at my PRMs and noticed that Wimp_Send!essage says: event code (as returned by Wimp_Poll – often 17, 18 or 19).
Does this imply that I can send Wimp events like clicks and menu selections to a program by abusing Wimp_SendMessage? I’ve never really considered that SWI out of the context of….what it says on the tin, sending messages between tasks.

Does this imply that I can send Wimp events like clicks and menu selections to a program

Yes, and this is mentioned in the PRMs, top of page 3-197 (dead wood edition).

Virtual desktops such as MoreDesk use it to move to next screen and to fetch windows (by sending an OpenWindow events). KeyStroke sends MenuSelection events (and more).

Good examples !LaunchApp and TrargetApp, thanks for sharing the code.

Does this imply that I can send Wimp events like clicks and menu selections to a program by abusing Wimp_SendMessage?

The click is the event. It is communicated by a message. SendMessage sends messages. Using it to send messages (even when there wasn’t an event) is not an abuse.