Glow effect causes exception in Forms.DoActionIdle

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #35608
    tomkrysl
    Participant

    Hello,

    This is a bug report for AC version 8.15, skin is Shine (internal), also chosen from this package.

    Bug is present only if SkinManager.Effect.AllowGlowing = True and causes a List index of bounds(6) exception in Forms.DoActionIdle, where at the moment of pressing the TsBitBtn the property Screen.CustomFormCount does not match the property Screen.CustomForms, exactly Screen.CustomFormCount is by one higher than Screen.CustomForms. Somehow the form with window procedure acGlow.TacGlowEffect.NewWndProc disappears a short time sooner from the list than Screen.CustomFormCount gets updated.

    I am sure it is a bug in AC because when I disable the skinning or the AllowGlowing property the application behaves normally and I never had such problems with the app with AC version 7.68 or older.

    Also I tested with skin Opus and there is no such error so maybe it is skin-dependent error?

    I cannot send the app or form for test because it is commercial app and this behavior cannot be tested without a physical device the app is connecting to.

    I disabled AlloGlowing property to overcome this.

    Regards

    TK

    #50016
    Support
    Keymaster

    Thank you for information, I will research it. Do you know how can I reproduce an issue?

    Maybe you can cut off all code from your application and send me this project?

    #50022
    tomkrysl
    Participant
    'Support' wrote:

    Thank you for information, I will research it. Do you know how can I reproduce an issue?

    Maybe you can cut off all code from your application and send me this project?

    Unfortunately this is not possible. I'm afraid it can be reproduced only in the whole app when connected to the device we sell.

    It seems to be somehow dependent on timing of the messaging processing.

    The only suplementary information I can give in version 7.68 it was ok and in version 8.14 and 8.15 it was not ok.

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