I created a script on the deactivate event on a form that closes it when the user moves away from the current window. This was discussed in this thread:
The problem I have now is when I try to edit the form. If I choose to edit it from the view mode, it closes the form. ---It's basically doing what I asked because it's not active any more. Not a huge problem because I can still access design mode through the control panel.
The weird thing that has happened, at least twice, is between my moving back and forth this way, I've lost the code editor window.
I thought it was gone for good, but come to find out, it was placed about 30 screens to the right, and I didn't put it there. I found it by moving the bottom scroll bar all the way to the right, and there it was. I had to drag it back into the working area or maximize the alpha5 work area to see it. It has only happened to the code editor window (none others) and only since I've put a "close command" on an event.
I guess I have three questions:
Thanks,
Brad
PS. Don't put a close command on the onexit event unless you want to close a second random window (which might be your control panel). Talk about crazy!
The problem I have now is when I try to edit the form. If I choose to edit it from the view mode, it closes the form. ---It's basically doing what I asked because it's not active any more. Not a huge problem because I can still access design mode through the control panel.
The weird thing that has happened, at least twice, is between my moving back and forth this way, I've lost the code editor window.
I thought it was gone for good, but come to find out, it was placed about 30 screens to the right, and I didn't put it there. I found it by moving the bottom scroll bar all the way to the right, and there it was. I had to drag it back into the working area or maximize the alpha5 work area to see it. It has only happened to the code editor window (none others) and only since I've put a "close command" on an event.
I guess I have three questions:
- Is this a bug that needs reporting?
- Will I have a problem when I'm using my application normally, so is this a safe way to keep the user from leaving this window open?
- Is there conditional code to wrap around this close statement to keep it from doing weird things? (I guess I need to know what the weird things are first before I can avoid it.)
Thanks,
Brad
PS. Don't put a close command on the onexit event unless you want to close a second random window (which might be your control panel). Talk about crazy!