|
From: Jo E. S. <jo...@on...> - 2025-09-24 10:22:46
|
On Wed, 24 Sep 2025 00:36:18 +0200, Thorsten Otto via Freemint-discuss <fre...@li...> wrote: >> Hm, that would certainly be useful. But maybe we can find a different solution >> for this. After all, the alert pipe is not only used to report access The program displays all alerts coming in from the pipe, crash/memory violation alerts are automatically detected and the "crash assistant" UI is only used for these. But some API with more details would of course be better. E.g. I have to periodically poll the process list to be able to display details about the crashed process, as the process is gone once the alert is sent. So in some cases where the program crashes immediately after start the location of the binary is unknown and the "restart" feature won't work. >> violations, but can contain any text. Looks like all the current program that monitors this pipe (XaAES, MultiTOS' alert.prg) expects the text to be formatted as an alertstring and does not display anything if it isn't. As I mentioned in another post - this is a bit weird and it should be up to the UI to decide how to present it. Btw my program does not care and displays the message regardless of format as long as it's plain text, but that's just a side-effect of the implementation. It can also show the alerts in a non-blocking window with automatic timeout, and it can show multiple alerts at once. So in theory the alert pipe can be used as a generic notification pipe. Jo Even |