On Sun, 19 Feb 2012 22:49:23 +0100, m0n0 <ole@monochrom.net> wrote:
XaAES can set the apid for the slb to the one of the caller, which fixes most issues, but it's still not a clean program and will kill the system sooner or later.can set or does set? There is really no need for that, DRACDLG.SLB should be fixed, it's really just 2 lines of code within the SLB and 2 lines for each project which uses dracdlg.slb ( at least when you want to make use of BubbleGEM, otherwise, the appl_init can be removed from the SLB without further work ).
You can remove the current appl_init() from the SLB and replace the "msg[n] = apid" with "msg[n] = appl_init()". This will work because the BubbleGEM-code in the slb is called in the context of the caller. The caller is already an AES client, so appl_init() will only return the caller's current apid.
This way there is no need to change anything in the programs that use this slb.
Jo Even