how to prevent XMAX OnStatus to overwrite the window status message?

[achu]

Is there a way "NOT" to write message to window.status bar?
OnStauts event will overwrite other useful/debugging messages displayed in the window status bar.


XMAX 5.5

[Derek Read]

I assume because you mention "window.status" you have XMAX sitting in an <OBJECT> in an HTML page loaded into IE?

XMAX shouldn't be doing anything to IE that you don't want it to. It has no idea which application it is embedded inside and so there is no direct communication with any specific IE properties even if that is the container application. Setting these types of properties, including "window.status" should be done with script, so I would look around inside your solution for a script that is setting this property.

[achu]

That's what I thought initially.
After taking "window.status" out from the script in my XMAX application, some status messages, such as importing 5% and turns rules checking on,  still take place in IE windows status bar.

[Derek Read]

You are correct, there are messages pumped specifically to IE (my mistake). I've created a completely bare test sample and can reproduce this. However, to the best of my understanding there will be no way to override these because we have no APIs designed for that purpose as far as I know.

I'm checking to see if someone here knows when those messages stop. I'm assuming it is once the document has successfully loaded, otherwise, I can't see a reason for implementing XMAX's "OnStatus" event (ie: I think it makes sense that you should be able to decide when to send messages up to IE, if at all, and where to send them).

[Derek Read]

Looks like this was an old design concept to provide some default capabilities when XMAX is embedded in a host application that supports a status propery (which includes IE). It saves you having to write the code that connects the two but unfortunately it also means you don't have control over it.

We'll re-evaluate this functionality for a future release but as of our current versions (up to and including 6.0) there isn't really anything you can do to alter this behavior.