Am 15.02.2012, 00:03 Uhr, schrieb m0n0 <ole@monochrom.net>:
Am Dienstag, den 14.02.2012, 23:37 +0100 schrieb "Helmut Karlowski" <helmut.karlowski@ish.de>:Am 14.02.2012, 23:19 Uhr, schrieb m0n0 <ole@monochrom.net>:Why does the SLB do an appl_init ???The line where the appl id is used is within the function show_help( ): ---------------- bubble_text = alloc_shared(256); if (bubble_text) { int msg[8]; strncpy(bubble_text, helptext, 255); bubble_text[255] = 0; msg[0] = BUBBLEGEM_SHOW; msg[1] = gl_apid; // <-- HERE IT IS
This must be the one of the caller!
msg[2] = 0;
msg[3] = x;
msg[4] = y;
msg[5] = (int)(((long) bubble_text >> 16)
& 0x0000ffff);
msg[6] = (int)((long) bubble_text & 0x0000ffff);
msg[7] = 0;
if (appl_write(bubble_id, 16, msg) == 0)
{
/* Fehler */
}
----------------------
no further usage of the appl id... But maybe it needs appl_init also
for alert's or whatever...? I don't know if it's enough to call
appl_init within the calling process....
The caller should inform the slb about it's apid (different for every user of the slb), or better the slb should not use the AES at all.
I wonder what apid it uses now when XaAES just returns in my patched version when the slb does appl_init ...
-- Helmut Karlowski