Skinned TPrintDialog Memory Leak v6.64

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #33931
    darcy
    Participant

    Hi,
    I have Version 6.64 installed and have found a serious issue which I believe is down to how AlphaSkins skins the TPrintDialog. I have created a very simple test app made up of only a TPrintDialog and button. When the TPrintDialog is launched (Execute command) and then canceled multiple times with the AlphaSkins enabled the memory used increments dramatically. When I disable/remove the skinning from the test app the memory problem does not occur.
    If testing in-house ensure to launch and cancel the TPrint dialog multiple times. Without skins enabled the memory increases slightly but then levels. With skins enabled it will increase on each Execute -> Cancel event.

    To help me work around this I have set the Skinning Rules to not include the StdControls. This is undesirable. Is there a further work around where I can target only the TPrintDialogs in my app rather than ALL the StdControls.

    Your speedy reply is greatly appreciated.

    Regards,
    D'Arcy

    #43194
    Support
    Keymaster

    Hello
    Dialog will not be skinned if you will change the srStdDialogs will be False (you can change it before calling of dialog immediately).
    What printer do you uses? I'll try to install a driver and will play with it.

    #43217
    darcy
    Participant
    'Support' wrote:

    Hello

    Dialog will not be skinned if you will change the srStdDialogs will be False (you can change it before calling of dialog immediately).

    What printer do you uses? I'll try to install a driver and will play with it.

    Hi,

    The printer type is a Dell 3110cn.

    During my investigation I also noticed how the size of my final exe increases dramatically when I have AlphaSkins enabled e.g. from 686kb to 2.4mb. As soon as a link in AlphaSkins using #pragma link the final exe JUMPS in size. Try it and see.

    #pragma link "sSkinManager"

    Is this a known issue and can I reduce/minimise this size increase? If I need to raise a new thread for this please let me know.

    Regards,

    D'Arcy

    #43265
    darcy
    Participant
    'darcy' wrote:

    Hi,

    The printer type is a Dell 3110cn.

    During my investigation I also noticed how the size of my final exe increases dramatically when I have AlphaSkins enabled e.g. from 686kb to 2.4mb. As soon as a link in AlphaSkins using #pragma link the final exe JUMPS in size. Try it and see.

    #pragma link "sSkinManager"

    Is this a known issue and can I reduce/minimise this size increase? If I need to raise a new thread for this please let me know.

    Regards,

    D'Arcy

    For info I have moved the question about the final exe size increase to the following thread in the Troubleshooting forum.

    http://www.alphaskins.com/forum/index.php?showtopic=5524

    I am still interested in know if the TPrintDialog memory leak can/will be resolved in the next release.

    Thanks

    #43269
    darcy
    Participant
    'darcy' wrote:

    For info I have moved the question about the final exe size increase to the following thread in the Troubleshooting forum.

    http://www.alphaskins.com/forum/index.php?showtopic=5524

    I am still interested in know if the TPrintDialog memory leak can/will be resolved in the next release.

    Thanks

    Hi,

    Has the above issue been addressed in Version 7.05 Beta:

    * Optimized initialization of standard and third-party controls

    Thanks,

    D'Arcy

    #43337
    Support
    Keymaster

    Hello

    'darcy' wrote:

    Hi,

    Has the above issue been addressed in Version 7.05 Beta:

    * Optimized initialization of standard and third-party controls

    Thanks,

    D'Arcy

    No, this message concerning a speed of controls initialization.

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