AC 6.3 Main form locking

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #32875
    Ralph
    Participant

    Just installed the new release. Thanks.

    Recompiled a complex project (main form and several custom forms) and ran. After closing (hiding) a custom child form the main form locks when I access the menus. If I turn AC active to false everything runs fine.

    Anyone else experiencing this problem?

    See Attachment:

    #38834
    Support
    Keymaster

    Hello Ralph
    Your Exe causes Exception on my machine, where skins must be placed? It's better when Exe have one internal skin…
    After recompiling your sources I haven't any problems (Delphi7 & WinXP). What Windows and Delphi version do you uses?

    #38849
    Ralph
    Participant

    QUOTE (Support @ Apr 27 2009, 07:48 AM)
    Hello Ralph
    Your Exe causes Exception on my machine, where skins must be placed? It's better when Exe have one internal skin…
    After recompiling your sources I haven't any problems (Delphi7 & WinXP). What Windows and Delphi version do you uses?

    Serge,

    My skins are in c:AlphaControlsskins. I will have an internal from now on for debugging purposes.

    Using D7 ent and Vista 64.

    Still have the same problem. in my example, did you
    start program
    Windows->form2
    Windows->form3
    Close form2
    then try any form1 menu? Totally locks my system.

    I have deleted and reinstalled 6.3 and still same problem.

    Turn off AC and all is okay.

    Can you replicate this problem?

    I still think this has to do with the title hints not counting correctly when forms are closed or ysytem icons are set to false.

    TIA

    RT

    #38879
    Support
    Keymaster

    I can't reproduce it at moment, but I'll try more soon.

    #38947
    Ralph
    Participant

    QUOTE (Support @ Apr 28 2009, 01:19 PM)
    I can't reproduce it at moment, but I'll try more soon.

    New Release solved the problem, thanks.

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