Remember me

Lost Password?

Register now!
Who's Online
68 user(s) are online (58 user(s) are browsing Forums)

Members: 0
Guests: 68

Support us!
Recent OS4 Files
Report message:*

Re: BOOPSI Menu Class: first update

Subject: Re: BOOPSI Menu Class: first update
by trixie on 2014/7/13 7:05:28

@chris, Rigo

For me personally, using callbacks in the Menu Class will only be a good solution if two conditions are met:

1. The low-level stuff (like allocating/freeing hooks) is handled by the class. BOOPSI is the highest-level component of Intuition so it had better behave like one; and as I've already said above, I can't imagine having to manage two dozen hooks on top of two dozen hook functions.

2. The callback function is a function that I need to write anyway - for example, an about() function that creates and displays the info requester - and which I can reuse and invoke from other parts of the program (such as the toolbar).

And there comes my current problem. If the about() callback is written as a hook function (i.e. with parameters required by the AmigaOS hook API) and is invoked by the class (which duly supplies the hook and all), how would I invoke the callback from the toolbar when there's no hook to pass as parameter?

The ARexx Class uses callbacks but doesn't use hook functions. This is something I'd like to know more about.
Powered by XOOPS 2.0 © 2001-2016 The XOOPS Project