Jump to content
Sign in to follow this  
ULIK

MMX 14.0.4 can't open Unit Dependencies with Delphi 10.2.3

Recommended Posts

Hi!

 

I noticed a bug on MMX 14.0.4: working on Delphi 10.2.3 I can no longer open the unit dependencies dialog as this throws an access violation:

command line       : "C:\Program Files (x86)\Embarcadero\Studio\19.0\bin\bds.exe" -pDelphi
executable         : bds.exe
current module     : madExcept_.bpl
exec. date/time    : 2018-03-09 14:55
version            : 25.0.29899.2631
compiled with      : Delphi 10.2 Tokyo
madExcept version  : 4.0.21
callstack crc      : $66537fdd, $000de4d0, $5b5c01d6
exception number   : 1
exception class    : EAccessViolation
exception message  : Zugriffsverletzung bei Adresse 208A1DF8 in Modul 'coreide250.bpl'. Lesen von Adresse 00000000.

main thread ($1bcc):
208a1df8 +034 coreide250.bpl     IDEServices      3095   +2 TIDEServices.ApplyTheme
20854e56 +042 coreide250.bpl     OTADockableForm   105   +2 TOTADockForm.EmbedFrame
20854db1 +06d coreide250.bpl     OTADockableForm    77   +6 TOTADockForm.Create
2085532e +08a coreide250.bpl     OTADockableForm   234   +9 TOTADockableFormManager.CreateDockableForm
208a4fdd +005 coreide250.bpl     IDEServices      4265   +0 TIDEServices.CreateDockableForm
5016dcd8 +004 rtl250.bpl         System.Classes  16816   +0 TBasicActionLink.SetAction
21a259c9 +03d vclactnband250.bpl Vcl.ActnMenus    1079   +6 TCustomActionMenuBar.ExecAction
21a2727c +124 vclactnband250.bpl Vcl.ActnMenus    1850  +19 TCustomActionMenuBar.TrackMenu
21a2acb2 +042 vclactnband250.bpl Vcl.ActnMenus    3644   +5 TCustomActionMainMenuBar.TrackMenu
21a2557d +029 vclactnband250.bpl Vcl.ActnMenus     958   +3 TCustomActionMenuBar.CMItemClicked
50ae4c5e +2be vcl250.bpl         Vcl.Controls     7338  +91 TControl.WndProc
50ae9843 +63b vcl250.bpl         Vcl.Controls    10209 +166 TWinControl.WndProc
21a27392 +0aa vclactnband250.bpl Vcl.ActnMenus    1889  +25 TCustomActionMenuBar.WndProc
50ae8e10 +02c vcl250.bpl         Vcl.Controls     9908   +3 TWinControl.MainWndProc
5016ebcc +01c rtl250.bpl         System.Classes  17408  +11 StdWndProc
75657885 +00a USER32.dll                                    DispatchMessageW
50c31e1f +0f3 vcl250.bpl         Vcl.Forms       10641  +23 TApplication.ProcessMessage
50c31e62 +00a vcl250.bpl         Vcl.Forms       10671   +1 TApplication.HandleMessage
50c32195 +0c9 vcl250.bpl         Vcl.Forms       10809  +26 TApplication.Run
7635343b +010 kernel32.dll                                  BaseThreadInitThunk

 

I checked it again with MMX 13.1 and here the dialog opens fine again. If it is related: IDE designs are deactivated on my Delphi installations.

 

kind regards,

Ulrich

Share this post


Link to post

I've done a test: if I enable IDE designs, then it is working again with 14.0.4. But it would be fine, if you find time to fix this (I prefer to disable the designs ,as on Windows 7 I find this better readable)

 

Thank you,

Ulrich

Share this post


Link to post
1 hour ago, ULIK said:

IDE designs are deactivated on my Delphi installations.

To be honest, I usually test only against an IDE with all options at default. It is near to impossible to test for all combinations. It was my hope that such things are discovered during the beta phase.

Share this post


Link to post
56 minutes ago, Uwe Raabe said:

It is near to impossible to test for all combinations.

You are right, this is not possible, and the main problem in these case is the IDE and OTA. Should work independent from the themes 

Share this post


Link to post

Well, the OTA contains a few special interfaces regarding themes and the Unit Dependency Analyzer was the first form (or better frame in this case) making use of those. What I didn't know (because as usual those things are poorly documented - if at all) is that it seems to be forbidden to call ApplyTheme when IDE themes are disabled. Not that this could as well be caught inside ApplyTheme (just for safety - instead of crashing), so that not everybody has to add this additional check in their code.

  • Like 3

Share this post


Link to post

Don't worry. It's fine to test against the defaults only. For all the special situations we have that group here to post the problems :classic_wink:

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
×