Auto created Toolbox objects/components

Right, I seem to be falling at the first hurdle here. I have created a UI in !ResED, I’ve gone with the whole auto-create thing, and the interface went together quickly and loads up just fine.

However, I registered an event to a button like so:

event_register_toolbox_handler(event_ANY, 0x2002,gourlhandler,NULL);

And that calls my ‘gourlhandler’ function just fine:
osbool gourlhandler (bits event_code,toolbox_action *action, toolbox_block *id_block,void *handle) {

}


So as I understand it, on clicking that button, id_block→this_obj will have the window object in it, and id_block→this_cmp will have the component ID in it. !ResTest would seem to back that up. However, on running, both those values appear to be the same pointer, and not valid.

Maybe I’m doing something stupid here, but my event gets called just as I planned, but the information coming to it seems like garbage. Why would the object and the component have the same value?

As always many thanks for the help…

Cheers

Garry

I’ll have a look how I do that when I get home.
One thing though, if you want to handle URLs i.e. so they open in netsurf etc. you can let AcornURI handle all that for you “automagically” which is what I do for newsuk.
I seem to remember it’s a case of setting the validation field or something like that.
I know generally I don’t use the icon handler and use a click in window handler and then just say if icon number X is clicked then ….
I think the refresh button may use a specific one though, so I’ll take a look.

That would be great Malcolm, thanks.

In fact the URL I am handling is one of my own creation, i.e. my own protocol, not http:, ftp: etc. so I need to handle it myself. My project is a network service, so I’m handling URLs myself.

Cheers

Garry

I’ve just started writing a socket handler, I’ve just started writing the module last night.
So it’s essentially just theoretical at the moment but, when that’s complete you should be able to:

SYS “QFA_Init”,socket,&handler_no,“news.bbc.co.uk”,“80”
SYS “QFA_Status”,handler_no,&any_data
while( any_data == 1 )
{
SYS “QFA_Get”,handler_no,data_buffer,10240
SYS “QFA_Status”,handler_no,&any_data
}
SYS “QFA_Close”,&handler_no

OR for http

SYS “QFA_Init”,http,&handler_no,“news.bbc.co.uk”,“80”, “/rss/feed.xml”, “SDFS::Harddisc0.$.test.xml”
SYS “QFA_Status”,handler_no,&any_data,&data_read,&data_total,&data_rate
while( any_data != 0 && any_data !=2 )
{
printf(“Reading data still.\n”);
SYS “QFA_Status”,handler_no,&any_data,&data_read,&data_total,&data_rate
}
if( any_data == 2 )
{
printf(“File downloaded…\n”);
}
SYS “QFA_Close”,&handler_no

The long term plan is to also include disc I/O and command processing as well as a network stack (imap/pop/dns/ssl/tls etc), but that is a long, long road!
My first aim is to offload the complexity of socket handling and http/ftp handling so a wimp task can call an SWI that will do all of the scheduling etc.
Ideally I’d like the SWI to use a wimp call to tell the program that called it the action has completed for it from QFA, such as “File downloaded”, or “Connection Refused” etc.

Initially it will be wget for RISC OS, I suppose. But designed for RISC OS rather than a “fudge port”.

The main reason is my programs are all going to be network related and having to redo basic network handling each time is making the code unmaintainable, sticking it in a module makes it highly portable.

Ideally I’d like the SWI to use a wimp call to tell the program that called it the action has completed for it from QFA

Via a pollword non-zero event?

er…Yeah ;-)
I knew there was someway of signaling wimp programs, I’ll store that for later.
Cheers!

Well for me I’m using id_block→self_component to get the icon number (component)

if( any_data == 2 )
{
printf(“File downloaded…\n”);
}
SYS “QFA_Close”,&handler_no

Cool. I’m not the only one to mix and mash languages in pseudocode.

Hmm, OK, I’m going to have to have another look at this then, id_block→self_obj and id_block→self_cmp appear to be the same thing in my struct, will need to see why that’s not working…

Interesting socket stuff, that’ll be something I’ll get to, hopefully once I’ve sorted out my UI stuff…

Cheers

Garry

Hmm, OK, I think I see what is happening. The toolbox_block which supplied to me in the event handler is NULL, however, the toolbox_block I set up when initialising my Toolbox application is populated with the correct info. Not sure if this is normal behaviour, but I can at least make my app work now.

Cheers

Garry