Skinned printer properties produces an AV (6.68)

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #43115
    HeDiBo
    Participant

    I found out that clearing all SkinningRules makes skinning the Printer Properties dialog go away. But that's too rigorous. I want standard warnings, etc. to stay skinned.

    #43135
    Support
    Keymaster

    Can you verify this dialog in the ASkinDemo.exe version 7, please? Many changes were made in the v7 and problem may be solved already.
    And can you show me a screenshot of dialog?

    You can disable srStdDialogs property before dialog showing and enable it after dialog closing. This dialog will not be skinned in this case.

    #43151
    HeDiBo
    Participant

    QUOTE (Support @ Aug 6 2010, 08:38 AM) <{POST_SNAPBACK}>
    Can you verify this dialog in the ASkinDemo.exe version 7, please? Many changes were made in the v7 and problem may be solved already.
    And can you show me a screenshot of dialog?

    You can disable srStdDialogs property before dialog showing and enable it after dialog closing. This dialog will not be skinned in this case.

    These are the PrinterSetup screens for version 6 and version 7. They have exactly the same flaws:

    [attachment=4113:PrinterP…ngErrors.jpg] ( Version 6.68 )

    [attachment=4114:PrinterP…ersion_7.jpg] ( Version 7.04 )

    #43182
    Support
    Keymaster

    Hello

    Thank you for screenshots. Which HP printer you have installed?
    I'll try to install drivers and I will look this dialog on my PC.

    #43187
    HeDiBo
    Participant

    QUOTE (Support @ Aug 21 2010, 06:44 AM) <{POST_SNAPBACK}>
    Hello

    Thank you for screenshots. Which HP printer you have installed?
    I'll try to install drivers and I will look this dialog on my PC.

    The printer is a HP Color Laserjet CP1515n PCL 6 used over the internal network.

    #43189
    Support
    Keymaster

    Thank you, I see glitches now and I'll try to fix it soon.

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