Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 01 JUL 2002 06:41:38PM Paul Rule wrote:

It appears that the MSG up function is now modal. eg:

image=msg("","Processing":@fm:"U")

This is a problem when the message is left displayed and other user actions are required. eg: Click on something. Its also a problem when debugging and the message is left displayed. You have to log out to regain control. Does anyone know of a way around this. ie: Modality on/off.


At 01 JUL 2002 07:08PM Mike Ruane wrote:

Paul-

In the code you listed, you are passing a null as the first parameter of MSG. The first parameter should be the parent window.

Hope it helps-

Mike


At 02 JUL 2002 06:29PM Paul Rule wrote:

Mike, I've tried it with @window as the first parameter and it still functions the same.


At 02 JUL 2002 07:03PM David Kafka wrote:

Paul,

Modal with respect to what? It is modal with respect to the @WINDOW, but unless you specify in the parameters, I don't think it's system modal. Just speculating, if nothing else seems to work use a hidden window as the parent?

Regardless, when debugging, I've found that ALT-F4 where close an errant message window.

David


At 03 JUL 2002 12:41AM Paul Rule wrote:

Thanks David,

Alt-F4 solves half of my problem. At least now I've got a method of removing the unwanted messages.

As to the modality side of it, I'm not sure. The problem is, that when these messages are displayed, user input is disabled, unlike OI16 where it wasn't.


At 03 JUL 2002 06:51AM Mike Ruane wrote:

Paul-

The parent won't necessarily be @window- you should use the parent as it is used in whatever program is being being called. You can also look in the online help for PARENT property.

MIke

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/794b37d9068f43e285256be9007ca9a7.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1