CompuServe Messages

Wolf, >> I just have to ask Werner more questions although I'm the uploader of the Demo, I'm not the programmer of Diavolo, but was a beta tester of V 3.0 (well, Martin made me the first on the list because I took so much pain for testing). The programmer's name is Martin Korndoerfer (m.korndoerfer@nathan.gun.de). I will report to him the filter bug that I mentionned – I blame myself on having it not found earlier. The crash problem when aborting Diavolo requesters has been solved in V 3.0. In the previous release version, it could be work-arounded by setting the task priority of the streamer task lower or equal to the priority of the harddisk task. And yes, when an error occurs or the backup medium has to be changed, the requester Diavolo sets up will become active. If Diavolo uses its own or another than the active screen, this screen will be pushed to front. So the behaviour of the requesters is very much the like as the SysRequests issued by AmigaDos when an error occurs. The problem is, in the case you are working with an editor at the same time, that the Diavolo requesters also accept the RET and ESC keys as an input, what may cause accidental replies. As a programmer, you may want to have a look at the API of Diavolo 3.0 Pro to customize the program to your needs. – wkc – … via AP from Hamburg, Germany