[cypheros]

It seems that the skinng of the TFileOpenDialog and TFileSaveDialog are not supported yet and skinning looks bad. This dialogs are working only for Windows Vista and newer versions.

TOpenDialog and TSaveDialog have a fall forward. If a newer Windows is detected, it's using the TFileOpenDialog and TFileSaveDialog.

But this is not working if skinning is active and I would like to have the newer dialogs.

If I disable StdDialogs in the SkinningRules, it's working but then all dialogs have no skinning.

How can I have the StdDialog skinned and the file dialogs not?

Sample application is attached and under settings you can change the skinning of StdDialogs to see the different dialog styles.

[Support]

TsSkinManager component have the OnSysDlgInit event with two params:

DlgData: TacSysDlgData

var AllowSkinning: Boolean

DlgData contains a Handle of dialog which will be skinned.

If AllowSkinning defined to False, then dialog will not be skinned.

Otherwise, you can wait, I plan add support of skins to such file dialogs.

[cypheros]

'Support' wrote:

TsSkinManager component have the OnSysDlgInit event with two params:

DlgData: TacSysDlgData

var AllowSkinning: Boolean

DlgData contains a Handle of dialog which will be skinned.

If AllowSkinning defined to False, then dialog will not be skinned.

Otherwise, you can wait, I plan add support of skins to such file dialogs.

How can I find out the type of the dialog or the component the dialog is belonging to?

DlgData.WindowHandle gives me only the handle of the dialog window and I can't find a connection to the TOpenDialog.

GetClassName is '#32770' and GetWindowName is '' for all Systemdialogs.

[Support]

So, we have only a Handle of the dialog when this system dialog is shown.

We can search there some controls which are specific only for File Dialogs.

You can search the “travelband” window there. If such window exists then this dialog is a File Dialog.

[Author]

Posts