trixie wrote:However, I'm still wondering how this message identifies the AmigaGuide client that was closed. An application can open several asynchronous AG clients (i.e. obtain several AG handles) and then Wait() for the close message - but how do I know which handle this particular message refers to?
Could we please have someone file a bug report and ask for a quick fix? I'm quite sure the reason for the message not being sent is something trivial.
Surely the different clients would have different signal number, so you'd just Wait(agSig1 | agSig2) and then check which signal was received before getting the message
trixie wrote:Makes sense. But then the number of asynchronously opened clients is limited to 16?
trixie wrote:So my and Chris' request here is either a bugfix (if ShutdownMsgID is indeed meant to signal client window closing), or a feature request (if such notification is not implemented at all). Pretty please
Maybe you could summarize the problem with a simple example program? Then I could create a bug report myself and attach that.
trixie wrote:But maybe Chris already has a piece of code that would demonstrate the problem?
There is also one other thing I'll need to investigate further. When you open an asynchronous AG client and the user presses the "Help" button in the window, the system-provided AmigaGuide help file will get loaded, "taking over" of your client. This wouldn't be a problem but it seems that there's no way for you to resume control, apart from shutting down and restarting the client (or pressing "Retrace" manually to get back to your file). This is rather stupid, as commands sent to the client will now be executed upon the AG system help file, not the file with which you opened the client. But as I say, I'll need to give it some more testing.
Users browsing this forum: No registered users and 1 guest