FiveTech Software tech support forums

... If you resize it to much the "bitmap" can't be paited, then it is reason for why the skin disapear. then you need adjust the oDlg:aMinMaxInfo to avoid that :D in case you want some different style you can make your own by editing the BMPs, please check the folder black_skin, blue_skin ...

... If you resize it to much the "bitmap" can't be paited, then it is reason for why the skin disapear. then you need adjust the oDlg:aMinMaxInfo to avoid that :D in case you want some different style you can make your own by editing the BMPs, please check the folder black_skin, blue_skin ...

... Even if you modify the size of oWndClient, the child windows will exceed its area, it is the way Windows is designed. You may try to use oWndChild:aMinMaxInfo to restrict the child dimensions ok But for a sample If I move on left and on top I can set the position of child wnd  if ::oWinTest:nLeft ...

Dear Silvio,

Even if you modify the size of oWndClient, the child windows will exceed its area, it is the way Windows is designed.

You may try to use oWndChild:aMinMaxInfo to restrict the child dimensions

... TITLE cTitle STYLE WS_POPUP oDlg:bStart := {|| oSkin := Skin( oDlg, "Blue_skin" ) } ACTIVATE DIALOG oDlg center I tried also with o Dlg:aMinMaxInfo := { nil, nil, ,, 600, 350,600, 350 } but not run

Mira a ver si esto te ayuda
viewtopic.php?f=3&t=34500&p=204878&hilit=aMinMaxInfo#p204878

... I used DEFINE DIALOG oDlgTariffe SIZE 880,600 ; PIXEL TRUEPIXEL RESIZABLE FONT oFont oDlgTariffe:aMinMaxInfo := { nil, nil, nil, nil, 878, 570, nil, nil } //878, 570 oDlgTariffe:bResized := <|| local oRect := oDlgTariffe:GetCliRect() local x:= ...

... many btnbmps. when I resize this window the procedure should reduce all the btnbmps that are inside up to a min / max that I set with oWndMain:aMinMaxInfo := { nil, nil, nil, nil, 878, 570, nil, nil } I talk of 450 btnbmps and on widow there is also a ribbonbar How I can resolve... I saw on ...

...  @ 195,250 BUTTON oBtnClose PROMPT "&Exit" SIZE 40,15 PIXEL OF oDlg ACTION oDlg:End()    oDlg:aMinMaxInfo = { GETSYSMETRICS( 0 ), GETSYSMETRICS( 1 ),;  // xMaxSize,      yMaxSize        ...

... * 0.85 ) Local nMAXWidth := GETSYSMETRICS( 0 ) //risoluzione orizzontale Local nMAXHeight := GETSYSMETRICS( 1 ) //risoluzione verticale ::oWndMain:aMinMaxInfo = { GETSYSMETRICS( 0 ), GETSYSMETRICS( 1 ),; // xMaxSize, yMaxSize 0, 0,; // xMaxPosition, yMaxPosition nMINWidth, nMINHeight,; // xMinTrackSize, ...

oWnd:aMinMaxInfo := { ; xMaxSize, yMaxSize, ; xMaxPosition, yMaxPosition, ; xMinTrackSize, yMinTrackSize, ; xMaxSize - xMaxPosition, yMaxSize - yMaxPosition } // xMaxTrackSize, yMaxTrackSize

Robb,

I am emailing you modified FWH 64 libs to test aMinMaxInfo and to confirm the wrong behavior of drag and
drop (you will get a visual confirmation).

You can test both using FWH\samples\testsize.prg and testdrop.prg

many thanks for your feedback

... array that winds up being passed in aFiles is always empty. No issues with 32 bit at all in this regard. The other issue has to do with using the aMinMaxInfo array to set min/max sizes for the main window. I protect the call to set these values so that they don't get used when running 64 bit. ...

... 900 local nMAXWidth := 1200//GETSYSMETRICS( 0 ) //risoluzione orizzontale local nMAXHeight := 900//GETSYSMETRICS( 1 ) //risoluzione verticale oWnd:aMinMaxInfo = { GETSYSMETRICS( 0 ), GETSYSMETRICS( 1 ),; // xMaxSize, yMaxSize 0, 0,; // xMaxPosition, yMaxPosition nMINWidth, nMINHeight,; // xMinTrackSize, ...

...  2911  2922  2931  3300  3312  3316                   3317  3318  3319  3322 AITEMS                  WINDOW.PRG     1768  1769  1770  1771  3438 AMINMAXINFO            WINDOW.PRG      445   617   618 APARENT1                WINDOW.PRG     4019  4022  4025  4028 APARENT2                WINDOW.PRG ...