- This topic has 10 replies, 4 voices, and was last updated 14 years, 5 months ago by Support.
-
AuthorPosts
-
May 7, 2009 at 9:31 am #32934OldGrumpyParticipant
Hi there,
I just downloaded and installed the trial version of AC 6.22 yesterday. After a bit of struggling with a funny bug in the AC converter, I managed to compile my app without errors, but the app crashes on startup with a stack overflow. It's tedious to debug this without the source, but maybe someone has an idea what I can check to find out where this stack overflow comes from. The stack is filled with an endless repetition of these lines:
So I guess it's stuck somewhere in the skinning process but I have no idea where to search. The application is rather huge, so I'd be really thankful for some ideas like “this can happen if you do [this] and [that]” or “check for [something]”…
Thanks a heap in advance! (no pun intended
May 7, 2009 at 9:44 am #39055SupportKeymasterHello
Could you send me Dfm-file of the form which have this error?
Also be sure that you not uses skins from the version 6.31, because new properties was occured there and some problems are possible.May 7, 2009 at 12:31 pm #39063OldGrumpyParticipantQUOTE (Support @ May 7 2009, 11:44 AM) <{POST_SNAPBACK}>HelloCould you send me Dfm-file of the form which have this error?
Also be sure that you not uses skins from the version 6.31, because new properties was occured there and some problems are possible.How can i find out which form has this error? The stack overflow does not occur until after Application.Run has been executed. I recompiled the application in debug mode with full debug information and the callstack looks a bit more informative now, but still… ah well. I'm attaching the callstack, it seems to be stuck somewhere around skinning a TSpeedButton.
About the skin version: I downloaded cold.asz from the gallery, options.dat inside states a version of 6.14 so it should work, right?
May 7, 2009 at 12:53 pm #39064SupportKeymasterThank you
I'm interested in form which must be shown first.
Also, what version of Windows and Delphi is used?May 7, 2009 at 1:10 pm #39066OldGrumpyParticipantI found the problem meanwhile. This application (rather “legacy”) has a lot of programmatically instantiated controls and passes references to GUI elements around. Some of those escaped the renaming process so that one panel and its child controls still were TPanel etc. instead of TsPanel. You can't see that in the DFM anyway, just in the *.pas. Thanks for the blazing fast support, though. Delphi version is BDS 2006, Windows is XP Pro SP3 (all updates performed). My application works properly now, I just need to rearrange some controls to make room for the eye candy
May 7, 2009 at 1:20 pm #39067SupportKeymasterThank you
May 11, 2009 at 1:22 pm #39113OldGrumpyParticipantQUOTE (Support @ May 7 2009, 03:20 PM) <{POST_SNAPBACK}>Thank youMay 12, 2010 at 8:18 pm #42494Владимир скромныйParticipantBut when we can wait new convertor?
May 15, 2010 at 12:10 pm #42522SupportKeymasterQUOTE (Владимир скромный @ May 12 2010, 11:18 PM) <{POST_SNAPBACK}>But when we can wait new convertor?
After the version 7 release, I can't tell more precisely..June 1, 2010 at 2:41 pm #42695Anderson PeterleParticipantHi Support,
I'm a new registered user and waiting for new version of converter too!!!
Best regards!
June 12, 2010 at 3:53 am #42746SupportKeymasterHi
QUOTE (Anderson Peterle @ Jun 1 2010, 05:41 PM) <{POST_SNAPBACK}>I'm a new registered user and waiting for new version of converter too!!!What you expect to see in this new version?
AuthorPostsViewing 11 posts - 1 through 11 (of 11 total)- You must be logged in to reply to this topic.