Hi,

During the build of this Maintain Application , there is one thing that bugs me quite a lot .

Everytime is close the application,i get a warning window stating

" This Application has been disconnected from the server"

Can i get rid of it , in anyway?


Im on Maintain 5.3,by the way

Any Ideas?


Peter

Pete
This usually happens when you click on the X on the toolbar instead of a clean exit. If you place an exit button on the form with a:

self.winexit();

command behind it, you will no longer get that error.

Mark

Mark,

the next question would then be .. how can i disable the X on the toolbar

cause you can count on it the users will click on it to close the application *smile*

is there a way to disable it

P.

Pete
We have never come up with a good way to do this. The X is a function of the browser. We have gotten creative and made the screen wider than the size of the browser. This way, the X appears off the screen.

Mark

In the onLoad Javascript for your form add the following bolded code.

var OriginalOnload = document.body.onload;
document.body.onload = LoadFunct;
window.onunload = unLoadMaintain;
function LoadFunct() {
if (OriginalOnload) OriginalOnload ();
}

function unLoadMaintain(){
OnbtnExit_Click();
}


Add a button to the form and name it btnExit. Add the “self.WinExit()” code from the close project button.

Case OnbtnExit_Click
self.WinExit();
EndCase

When the red X of the window is clicked, the unLoadMaintain function is called, unloading maintain and disconnecting from the server.

Good luck

Steve

I believe that you can also add

MNTCON EXIT_WARNING OFF

in EDASPROF.PRF (or user profile) to get rid of the message.

That's true, however it can leave an agent hanging on the server.

Cannot remember what happens in the 5.n releases now, but in 7.6 the agent will not hang, but will move to an idle state even if the browser is closed incorrectly when in a Maintain.

4.n releases will leave the agent hanging.

I believe that Maintain is pretty robust now and many of the older issues no longer apply. It is also difficult to intercept the generated js, and I now do not attempt to do that.

The one thing I did find was that by adding a further window.onload caused the generated window.onload to fail, and suspect adding another window.onunload may have the same effect, it may be better to use a window.onbeforeunload to save any issues with js processing if you want to go down that road.

In the Top case of your Maintain file --

   Sys_mgr.focset("maintain_warning", "off")