Modal dialog appears to be off the screen/cannot access
Posted: Thu Jan 21, 2016 9:48 am
I have suspected this from time to time and now have more information. I am going to try to duplicate it.
User was doing an account flagging process. The are working in other applications while this process is working. During the process, it locks accounts when needed and requests retry of locks automatically for a certain period and then pauses with a dc_msgbox popup asking to retry the lock process. The accounts are only temporarily locked when they are being worked on.
Again, this user workings in other Xbase++ and windows applications when this process is running, which may take 5-10 minutes.
When they came back into the Xbase++ application, the application appeared to be hung as the progress bar was not moving. In actually, the dc_msgbox was active, as a modal box, but off the screen. We were able to pull up the array/object and it showed the following:
OBJECT:DC_XbpDialog1 [Confirmation] [P:-32076,32891] [S:236,189]
Now I was able to partially duplicate the problem because something with the MODAL and SETAPPFOCUS is not working as the DC_MsgBox() yes/no dialog was not behaving as a modal. However, when I look at the same information, the position was [P: 837, 866].... and as expected. I could click the dialog and respond to it. However, with the problem position, it is off the visible screen and I don't know specifically how that happened. I have seen it before and suspect a similar situation to be the cause of potentially most of my unexplained system freezes.
How can I prevent this, provide a methodology to allow the box to be re-positioned to the visible screen and on top of the application.
User was doing an account flagging process. The are working in other applications while this process is working. During the process, it locks accounts when needed and requests retry of locks automatically for a certain period and then pauses with a dc_msgbox popup asking to retry the lock process. The accounts are only temporarily locked when they are being worked on.
Again, this user workings in other Xbase++ and windows applications when this process is running, which may take 5-10 minutes.
When they came back into the Xbase++ application, the application appeared to be hung as the progress bar was not moving. In actually, the dc_msgbox was active, as a modal box, but off the screen. We were able to pull up the array/object and it showed the following:
OBJECT:DC_XbpDialog1 [Confirmation] [P:-32076,32891] [S:236,189]
Now I was able to partially duplicate the problem because something with the MODAL and SETAPPFOCUS is not working as the DC_MsgBox() yes/no dialog was not behaving as a modal. However, when I look at the same information, the position was [P: 837, 866].... and as expected. I could click the dialog and respond to it. However, with the problem position, it is off the visible screen and I don't know specifically how that happened. I have seen it before and suspect a similar situation to be the cause of potentially most of my unexplained system freezes.
How can I prevent this, provide a methodology to allow the box to be re-positioned to the visible screen and on top of the application.