 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
 Posted: Sat Oct 20, 2007 5:38 pm
[2.07] More settings destruction
|
I doubt this is replicatable at all, but I will hold onto to the package file that shows this. This occurred when I moved a class from one package to another with a right-click Move To. The portions of the trigger visible outside of the window and module actually belong to a trigger in a disabled class nested in the one I moved. Everything within that class seems to have been lost except for an alarm.
Opening this package in a untitled session, then removing the package from the session causes this crash.
| Code: |
date/time : 2007-10-20, 13:51:07, 639ms
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 1 day 5 hours
program up time : 30 seconds
processor : AMD Athlon(tm) Processor
physical memory : 94/383 MB (free/total)
free disk space : (C:) 13.97 GB
display mode : 1024x768, 32 bit
process id : $1c0
allocated memory : 26.70 MB
executable : cMUD.exe
exec. date/time : 2007-10-19 18:25
version : 2.7.0.0
madExcept version : 3.0b
callstack crc : $a6e6ad5c, $4d0cb6c9, $4d0cb6c9
count : 2
exception number : 1
exception class : Exception
exception message : Setting class to wrong record: 2.
Main ($cb4):
00d2f0d2 +082 cMUD.exe PrefDat 7464 +5 PkgData.SetDefClass
00d36314 +060 cMUD.exe PrefDat 10172 +7 PkgData.RestoreRec
00c56329 +bbd cMUD.exe PARENT 4521 +293 TParentForm.UpdateButtons
00c536bb +06f cMUD.exe PARENT 3281 +15 TParentForm.DoRefreshSetting
00c53710 +030 cMUD.exe PARENT 3295 +2 TParentForm.wmRefreshSetting
00505f93 +1df cMUD.exe Controls 4645 +53 TControl.WndProc
00509cc2 +18e cMUD.exe Controls 6342 +33 TWinControl.WndProc
00526da0 +478 cMUD.exe Forms 3098 +103 TCustomForm.WndProc
00bfc6f4 +020 cMUD.exe DXSounds 2013 +9 TCustomDXSound.FormWndProc
00bf9e50 +00c cMUD.exe DXClass 572 +1 TControlSubClass.WndProc
00509894 +034 cMUD.exe Controls 6237 +3 TWinControl.MainWndProc
0047fef8 +014 cMUD.exe Classes 10966 +8 StdWndProc
77d4e361 +016 USER32.dll CallWindowProcA
006d6243 +0a7 cMUD.exe aqDockingUtils 1728 +7 CallDefWndProc
006d6331 +0dd cMUD.exe aqDockingUtils 1776 +41 TaqWindowEventFilter.WndProc
0047fef8 +014 cMUD.exe Classes 10966 +8 StdWndProc
77d4bcc7 +00a USER32.dll DispatchMessageA
0052ee48 +0ac cMUD.exe Forms 6873 +13 TApplication.ProcessMessage
0052ee8f +00f cMUD.exe Forms 6892 +1 TApplication.HandleMessage
0052f12a +0a6 cMUD.exe Forms 6976 +16 TApplication.Run
00dba9f4 +088 cMUD.exe CMUD 344 +18 initialization
7c91312f +069 ntdll.dll RtlUnicodeStringToAnsiString
7c812907 +0b6 kernel32.dll GetVersionExA |
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Oct 22, 2007 7:40 pm
|
Can you be more specific about the contents of the class that you moved? Were these trigger conditions that ended up in the root the conditions under the alarm that was moved? If you could show me the XML of what was in the class before you moved it, that would really help.
|
|
|
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
