Dear All, Thanks for all help&idea, It is true as Rao said but Manuel idea is work well for my solution. Because this screen is work for viewing the interface record. http://img20.imageshack.us/img20/7595/smsrrx.th.jpg Hello Dutch: I create Main Windows and xBrowse. The probl...
Mr Mercado's suggestion works. But even this has a few side effects in that the MDI childs do not get painted properly at times and when maximized we cant see the close, resize and minimize buttons, etc. Basically we should keep in mind that we are trying to do something not intended.
dutch wrote:I create Main Windows and xBrowse. The problem is xBrowse on Main Windows is not active. It cannot click, scroll and any action but refresh() is still working.
Try by creating the control over oWnd:oWndClient ( not over "oWnd").
>Child windows get created behind the dialog. I believe this is a limitation of MDI. Personally, I do not like MDI. Consider a SDI design with splitter on a main window and put the main browse on one side and the others on the other side. This way the user doesn't have to move windows around. James
Thanks for the lead. But this solution has problem. Child windows get created behind the dialog. We need the xbrowse on the frame like the background, but functional
I agree with Rao, it works only with a little help from a Dialog : http://www.pflegeplus.com/pictures/embedd1.jpg I wanted to calculate the Browse-Width and Hight with using oDlg0:nHeight and oDlg0:nWidth, but it didn't work and I had to find out the Bottom (-133) - and Right-Border ...
Do you mean XBrowse on MDI Main window ? To my knowledge no controls work on MDI main window. If there is a way I am also very much interested to know.
Dear All, I create Main Windows and xBrowse. The problem is xBrowse on Main Windows is not active. It cannot click, scroll and any action but refresh() is still working. Why I put xBrowse to main windows, because it is interface program. It is waiting for the record and automatic action some routine...
... Menu is still active ( which it should be ) .. however, the _Rptmenu() is an MDIChild and I use BuildMenu3() to blank out the MDI menu to imake it inactive. What I would like to do is disable the MDI oMenu line in the start of _Utilmenu() and then I can restore it on the way out. Here is the code ...
Con todo gusto Manuel y disculpa la tardanza. Estuve varios días sin utilizar la red. Con DrawFrameControl() puedes dibujar todos estos "objetos" de windows: #define DFC_CAPTION 1 #define DFC_MENU 2 #define DFC_SCROLL 3 #define DFC_BUTTON 4 *#if(WINVER >= 0x0500) #define DFC_POPUPMENU 5 *#endif /...
... (::moveColumn() or ::exchange()) DATA lNoExit AS LOGICAL INIT .F. // prevents edit exit with arrow keys DATA lNoGrayBar AS LOGICAL // don't show inactive cursor DATA lNoHScroll AS LOGICAL // disables horizontal scroll bar DATA lNoLiteBar AS LOGICAL // no cursor DATA lNoMoveCols AS LOGICAL INIT ...
... them to nothing. While in ADO.2 setting the connObj to nothing removes the connection from the pool, in ADO 2.1, the connection only becomes inactive and waits in the pool until, or if, it is needed. The final bit of code for this is: rsObj.Close Set rsObj = Nothing connObj.Close -------------------------------------------------------------------------------- ...
... still being used by our clients In summary the reason for the Clipper application runs very slowly is because XP incorrectly thinks the app is inactive and then reduces its cpu cycles. XP thinks it is inactive because all the DBF activity is replaced with communications between the Clipper ...
... cells at editing time. f).- Text and background in columns that controls the index. g).- Text and background in focused cells when the browse is inactive. h).- Grid lines. The manage of colors goes up to cell level (not only lines or columns), you'll see the sample programs. Colors can be assigned ...