FiveTech Support Forums

Hi Silvio,

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 and simple_skin ( inside samples of fwh ).

Any question let me know.

Silvio.Falconi wrote:

Dear Silvio,

Look at this! Thanks to Master Lailton! :-)

EXE and new theme:
https://github.com/FiveTechSoft/FWH_tools/blob/master/mdi_skin_w11.zip

playing with the window I got this error



so i did a test on all three window types and i saw this



however even in the dialog there is some error if for example I use a resizable dialog with a folder inside it gives me an error in the sense that it shows the interface incorrectly as you can see below



dialog source

Code (fw): Select all Collapse

#include "fivewin.ch"
#include "constant.ch"

Function Configurazione()
   local oDlg, oFld,oFont,oBold
   local oBtnConfirm,oBtnClose
   local aprompts:={"Azioni all'avvio","Aspetto Interfaccia","Connessioni","Premi"  }
   local cTitle:= "Configurazione applicazione"
   local oSkin
   local aGet:=array(30)
   local oSay

DEFINE FONT oFont NAME "MS Sans Serif" SIZE 0, 12
    DEFINE FONT oBold NAME "MS Sans Serif" SIZE 0, 12 BOLD

DEFINE DIALOG  oDlg ;
      SIZE 500, 250  PIXEL TRUEPIXEL RESIZABLE ;
      TITLE cTitle     COLOR 0, CLR_WHITE FONT oFont  STYLE WS_POPUP

       @ 1,1 FOLDER oFld Prompts aprompts OF oDlg;
               SIZE oDlg:nWidth-5,oDlg:nHeight-30




     @ 100,10 Say oSay Prompt  "NB. Le modifiche saranno effettive al prossimo avvio del programma" of oDlg SIZE 350,18 PIXEL  TRANSPARENT
     @ 100,10 BUTTON oBtnConfirm PROMPT "OK" of oDlg  SIZE 80,22 DEFAULT ACTION ( oDlg:end( IDOK  ) )
     @ 100,10 BUTTON oBtnClose PROMPT "Annulla" of oDlg  SIZE 80,22 CANCEL ACTION ( oDlg:end( IDCANCEL ) )





 oDlg:bResized  := <||
        local oRect        := oDlg:GetCliRect()
        oSay:nLeft    := oRect:nLeft+5
        oSay:nTop     := oRect:nBottom - 25
                oBtnConfirm:nLeft    := oRect:nRight - 200
                oBtnConfirm:nTop     := oRect:nBottom - 25
                oBtnClose:nLeft    := oRect:nRight - 100
                oBtnClose:nTop     := oRect:nBottom - 25
                oFld:nTop          := oRect:nTop
                oFld:nWidth        := oRect:nWidth - 10
                oFld:nHeight      := oRect:nBottom - 30
        return nil
        >
        oDlg:aMinMaxInfo := { nil, nil, ,, 600, 350,600, 350 }

          oDlg:bStart := {|| oSkin := Skin( oDlg, "Blue_skin" ),;
                       oSkin:this[ 10 ]:bLButtonUp := nil  ,;
                       oSkin:this[ 11 ]:bLButtonUp := nil ,;
                       oSkin:this[ 9 ]:bLButtonUp := nil }

 ACTIVATE DIALOG oDlg center ;
       ON INIT  ( EVAL( oDlg:bResized))

 return nil
//----------------------------------------------------------------------------------------------//

Lailton wrote:Hi Silvio,

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 and simple_skin ( inside samples of fwh ).

Any question let me know.

Hi Laiton,
I have to prevent end user operations in order to avoid problems, the fact of using oDlg:aMinMaxInfo can be a deterrent but I have seenon Tkin that the whole set is not fully functional, i.e. if the dialog is resizable and the user wanting to resize the dialog can do it but with difficulty because unlike the normal dialog when you approach the mouse to the edges fwh shows the cursor (arrows) to enlarge or shrink, with Tskin a effects myself I find it difficult to enlarge or shrink a dialog .

I still don't understand if using Tskin is the best solution, I really don't understand how other languages ( Delphi. Vb, C++ ) have Mdi Child windows in order to take the OS theme, and in fwh the windows have the style of win8/xp i.e. they do not have the same style of win10.

I am firmly convinced that perhaps a solution could be found, perhaps loading the net Dll like "CefSharp.WinForms.dll" or "System.Windows.Forms.DataVisualization.dll" to recreate the childwindows but I wouldn't be able

for a sample :https://help.syncfusion.com/windowsforms/form/mdicustomization


Aesthetically it wouldn't be nice to use different windows, I'm trying to understand if Tskin could work for both dialogs and windows, it's not about having different styles or colors, it's about having a working and homogeneous system

Dear Sylvio,

We can't use those .NET DLLs from Harbour

IMO Class TSkin is a very good solution

Hi Silvio,

I got it, then I dont think that TSKIN is what you want. the main idea about TSKIN is to make the dialog different.

I remember that window API too provide something like "UxTheme" https://learn.microsoft.com/en-us/windows/win32/api/uxtheme/nf-uxtheme-getwindowtheme
where is possitble to change some colors or read information about the theme. I have not used that because I was affraid it not works for all the Windows Versions, so for my needed the TSKIN in that moment was my solution.

Note:
My inspiration for the TSKIN was a DLL from "codejock" a commercial component to create skin, that works fine. but there is a price and a dependency to be added to your system ( I dont really like 3rd dll into my project ).
https://codejock.com/downloads/visualstyles.asp

I am sure if you search here on the forum by codejock you will find several post about how to use it in case you want to try.

Anyway, I hope you will find a best way to do what you want.

Happy New Year.

About codejock again,
It is the MDI example Silvio, You will like it :)

https://drive.google.com/file/d/1yVxDfcwI4EdB8Sh0JqGPmOkakiyCl_rT/view?usp=share_link

An example how to use it:
https://fivetechsupport.com/forums/viewtopic.php?f=3&t=15706&p=81371&hilit=CodeJock.SkinFrameWork&sid=5aebc763970f543731c8dbdb4a4cb911#p81371

IMO the best company with skin solution is that one. their TOOLKIT offer several kind of style.
( I dont use it actually, but looks fantastic :) )

Hi Lailton,

Is the RibbonBar also affected for this new class ? Could you show us an example with a RibbonBar?

Hey Vilian,

I have not tried that, you can try it by yourself if you are using ribbonbar. the skin code is one single line:
oDlg:bStart := {|| oSkin := Skin( oDlg, "Blue_skin" ) }

where the odlg can be dialog or window and the blue_skin is the folder that contains the skin. try and let us to know the result.

:D

Lailton wrote:Hi Silvio,

I got it, then I dont think that TSKIN is what you want. the main idea about TSKIN is to make the dialog different.

I remember that window API too provide something like "UxTheme" https://learn.microsoft.com/en-us/windows/win32/api/uxtheme/nf-uxtheme-getwindowtheme
where is possitble to change some colors or read information about the theme. I have not used that because I was affraid it not works for all the Windows Versions, so for my needed the TSKIN in that moment was my solution.

Note:
My inspiration for the TSKIN was a DLL from "codejock" a commercial component to create skin, that works fine. but there is a price and a dependency to be added to your system ( I dont really like 3rd dll into my project ).
https://codejock.com/downloads/visualstyles.asp

I am sure if you search here on the forum by codejock you will find several post about how to use it in case you want to try.

Anyway, I hope you will find a best way to do what you want.

Happy New Year.

can U make the same color theme of Win 10 ( I have Windows 10 Pro version 21H2) the header are smaller and are white color then the button are different , I tried But I not Know How make it easy...then I not Know win 11
just to have homogeneity between the theme of the main window and the sub windows , and then with the same system I can also use in the dialogs even if in the dialogs I have no theme problems, i.e. the dialogs respect the theme of the main Mdi , the sub windows child do not respect it, I will continue not to understand but I adapt

Lailton wrote:Hey Vilian,

I have not tried that, you can try it by yourself if you are using ribbonbar. the skin code is one single line:
oDlg:bStart := {|| oSkin := Skin( oDlg, "Blue_skin" ) }

where the odlg can be dialog or window and the blue_skin is the folder that contains the skin. try and let us to know the result.

:D

I haven't got this new version yet. Could you just test this with \fwh\samples\ribbon.prg for dark theme ?
I would love to know the result before update my FWH version ;)

Hola buenas tardes para todos, estoy intentando compilar el ejemplo skin3.prg, con la ultima versión de fwh, pero me sale el siguiente error:

Estimado Leandro,

Deberias tener dicho fichero en c:\bcc7\include\windows\crtl\string.h

Antonio gracias por responder, el archivo se encuentra en la ruta indicada en el bat buildx.bat

Obtengo el mismo error al intentar compilar erdsample.prg

Leandro,

En tu primer post, el error se produce al llamar al compilador de recursos:

Borland Resource Compiler Version 5.40
Copyright (c) 1990, 1999 Inprise Corporation. All rights reserved.

Error guiddef.h 147 11: Cannot open file: string.h

Luego es al compilador de recursos al que tienes que proporcionarle el path de string.h

Antonio como vas?

Que pena molestar de nuevo por esto, pero no comprendo cuando nos dices que debemos agregar esa información al compilador de recursos. No tenemos ni idea como se hace, jejejejeje no se cual es el compilador de recursos.

Tambien intente compilar el ejemplo desde fivedit, pero nos salieron estos errores
De antemano gracias

Estimado Leandro,

el compilador de recursos de Borland es el c:\bcc7\bin\rc.exe