FiveTech Software tech support forums

... You can do this by drawing a rectangle using functions like WndBoxClr, where you can specify the brush or pen color. Otto local hPen, oCli := ::GetCliRect() hPen = CreatePen( PS_SOLID, 1, nRGB( 255, 0, 0 ) ) WndBoxClr( ::GetDC(), 1, 1, oCli:nBottom - 2, oCli:nRight - 2, hPen ) DeleteObject( ...

... How I must set the scroll to have the same height of the xbrowse ? I made oDlg:bResized := <|| local oRect := oDlg:GetCliRect() oBar:nWidth:= oRect:nRight oBrw:nWidth:= oRect:nRight-290 oBrw:nHeight:= oRect:nBottom-45 oPanel:nTop := oRect:ntop +40 oPanel:nLeft := ...

... depending on whether the application is ANSI or Unicode. We can use simplified functions of FWH: GetClientArea( hWnd ) --> aRect oWnd:GetCliRect() --> oRect

... depending on whether the application is ANSI or Unicode. We can use simplified functions of FWH: GetClientArea( hWnd ) --> aRect oWnd:GetCliRect() --> oRect

... } ::oDtPick:bChange = { | o | ::ChangeDate( o ) } oPanel:bResized := <|| local oRect :=oPanel:GetCliRect() ::oDtPick:nWidth := oRect:nRight return nil > seem to run , but there is something bad

Leandro, los objetos de FW , tienen propiedades como nTop, nLeft, nBottom, nRight y otros metodos como GetCliRect() con los que puedes conseguir, la ubicación del objeto y su tamaño, en base a esa información podrías deducir lo que necesitas en función de la resolucion de ...

... oFont oDlgTariffe:aMinMaxInfo := { nil, nil, nil, nil, 878, 570, nil, nil } //878, 570 oDlgTariffe:bResized := <|| local oRect := oDlgTariffe:GetCliRect() local x:= oBrw1:nBottom oBtnCheck:nLeft := oRect:nRight - 395 oBtnCheck:nTop := oRect:nBottom - 50 oBtnPrint:nLeft := oRect:nRight - 220 ...

but GetCliRect() and GetCliAreaRect() doesn't work as expected

They always start with 0,0. That is to be expected.

but GetCliRect() and GetCliAreaRect() doesn't work as expected, nTop and nLeft are always 0
I then tried GetCoors() and it works:

The methods :GetCliRect() and :GetCliAreaRect() are doing exactly what I was looking for :!: Here are some posts regarding these two methods: http://forums.fivetechsupport.com/viewtopic.php?f=3&t=8733&p=41038&hilit=GetCliRect#p41038: ...

... lPageUp, lPageDown, lPos, nPosZugabe ) LOCAL i, aFirstWndCoors, nAltWert LOCAL nZugabe := 14 LOCAL nPageZugabe := 392 LOCAL aCliRect := oMainWnd:GetCliRect() DEFAULT lUp := .F. DEFAULT lDown := .F. DEFAULT lPageUp := .F. DEFAULT lPageDown := .F. DEFAULT lPos := .F. pausa(1) UnSelectAll() FOR ...

...  in ?)    WINDOW.PRG     1393  3237  3286  4061 GETCLIENTRECT()        (function  in ?)    WINDOW.PRG     1284  1291  1307  1314  1699  2946 GETCLIRECT()           (function  in ?)    WINDOW.PRG      604  1697 GETCOORS()             (function  in ?)    WINDOW.PRG     1425 GETDC()         ...

... nil     http://img443.imageshack.us/img443/1625/captureko.png Also, as you mention that the error is related to GetCliRect(), it seems as it may come from bar.prg lines 81 and 158. We could add this code to prevent from such error: METHOD New( oWnd, nBtnWidth, ...

This first screen shot shows the screen that always displayed correctly in the past. Now with 11.11 it gets the error I mentioned with GetCliRect being unknown. Note that each folder page has its own bar control plus the dialog has one. It will not activate the dialog as a result, so there ...

... each folder also. This works fine in the former xharbour/fwh10.9 build. However, with 11.11 and Harbour / MSVC, I get the error No exported method GetCliRect when trying to open dialog 2. Obviously, tbar was called with dialog 1, so there must be a problem with multiple bar controls now. They worked ...