SkinManager.SkinningRules question

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #35669
    Kujo
    Participant

    Hello to all,

    I have a question:

    if I use sMessageDlg, sShowMessage, sInputBox, etc… from sDialog unit, why I need to add “srStdDialogs” to the SkinningRules property ?

    srStdDialogs is not only for standard dialogs (like Messagedlg, ShowMessage, etc..) ?

    I ask this because I have a DLL with a skinned form that can be called from any EXE (not skinned): if the EXE needs to display a message (like ShowMessage) while the skinned form is visible, this message is skinned too and this is not correct.

    If I disable “srStdDialogs”, the message from EXE file is ok, but also the messages from the skinned form are not more skinned.

    Thanks.

    #50296
    Support
    Keymaster

    Hello!

    I'll try to improve it in the next Beta version.

    #50402
    Kujo
    Participant
    'Support' wrote:

    Hello!

    I'll try to improve it in the next Beta version.

    Hello,

    I tried the version 8.31, but the problem is still present.

    Another question: there is a reason why are not implemented the dialogs relative to the printers (eg: TsPrintDialog, TsPrinterSetupDialog)?

    Best regards.

    #50518
    Kujo
    Participant
    'Kujo' wrote:

    Hello,

    I tried the version 8.31, but the problem is still present.

    Another question: there is a reason why are not implemented the dialogs relative to the printers (eg: TsPrintDialog, TsPrinterSetupDialog)?

    Best regards.

    The problem is still present in the 8.32 version: if I remove the srStdDialogs option, the standard Windows dialog is shown instead to the skinned one. This is also true for the sOpenDialog, sSaveDialog, etc…

    #50524
    Support
    Keymaster

    Hello, sorry for a delay!

    After many thinkings I think, that it's a right behaviour now. sMessageDlg and sShowMessages uses MessageBox function from Windows API and this dialogs are standard dialogs too.

    srStdDialogs should control a skinning of all dialogs, I think.

    Quote:
    Another question: there is a reason why are not implemented the dialogs relative to the printers (eg: TsPrintDialog, TsPrinterSetupDialog)?

    Printer dialog is dependent from OS and from printer model. Different printers have different dialogs and it's not possible to make the universal dialog…

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.