|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Sat Oct 27, 2007 7:09 pm
[2.09] Another way to get package level settings |
I can't quite think of anything else to do with them, but here is how to make them.
1. Launch CMud (I am still working on finding a way to have a bug not require this step )
2. Close Sessions Window (ESC)
3. Open Package Editor (CTRL-G)
4. Make a new module, and give it a name
5. Make a new setting and give it a name
6. Right-click on your new module in the tree and select Delete
7. Answer No to the delete settings within question
Again I really can't think of where else they should go, so maybe this report is more of just a fishing expedition for ideas. At least that is what I was telling myself as I made the joke with step 1. |
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Sat Oct 27, 2007 9:03 pm |
Just to follow up on this, since I hadn't made a crash yet I decided I needed to find one . I went out of my way to try to create a situation that would crash. Oddly I couldn't forcibly create a crash, what I was thinking of had to do with this reported situation and CMud handled it perfectly. I was getting tempted to make a joke report about #TEST causing a crash, just because I thought that might be the only one I could find.
Settings outside of a module/window do cause a crash though, and it seems to be caused by trying either spell check or syntax display one of these settings. The crash has wildly swinging addresses for the error, the stack dump is always the same. The crash takes some patience to generate, but is replicatable. Some minor changes and additions to the steps above will cause it.
5. Make new alias, give it a name and put something in the script field
8. Left-click back and forth between the untitled window setting and the alias setting until it crashes
Code: |
date/time : 2007-10-27, 17:07:04, 194ms
operating system : Windows XP Service Pack 2 build 2600
system language : English
system up time : 8 days 9 hours
program up time : 1 minute 6 seconds
processor : AMD Athlon(tm) Processor
physical memory : 83/383 MB (free/total)
free disk space : (C:) 13.90 GB
display mode : 1024x768, 32 bit
process id : $18f4
allocated memory : 28.45 MB
executable : cMUD.exe
exec. date/time : 2007-10-26 22:15
version : 2.9.0.0
madExcept version : 3.0b
callstack crc : $02d8e190, $f6f25cc9, $f6f25cc9
count : 2
exception number : 1
exception class : EAccessViolation
exception message : Access violation at address 00D36E41 in module 'cMUD.exe'. Read of address 61272C33.
Main ($18f8):
00d36e41 +001 cMUD.exe PrefDat 10140 +2 PkgData.Get_Pref
00d332b1 +06d cMUD.exe PrefDat 8789 +4 PkgData.StripClass
00d51123 +51b cMUD.exe cMUDL 1089 +96 TCMudLImp.yylex
00d61a3e +0ce cMUD.exe CmudY 11271 +29 TCmudYImp.yyparse
00d57226 +092 cMUD.exe CmudY 321 +10 TCmudYImp.Execute
00ba9f89 +215 cMUD.exe zLexer 385 +58 TScintLexer.Parse
00cd5a04 +074 cMUD.exe EditScript 537 +13 TEditScriptF.EditorStyleNeeded
0090686b +017 cMUD.exe SciLexer 1939 +2 TScintillaBase.doSciStyleNeeded
00905d08 +0b0 cMUD.exe SciLexer 1197 +8 TScintillaBase.WMNotify
00505f93 +1df cMUD.exe Controls 4645 +53 TControl.WndProc
00509cc2 +18e cMUD.exe Controls 6342 +33 TWinControl.WndProc
00505c9e +036 cMUD.exe Controls 4552 +5 TControl.Perform
00509e84 +03c cMUD.exe Controls 6388 +6 DoControlMsg
0050a693 +017 cMUD.exe Controls 6579 +1 TWinControl.WMNotify
00505f93 +1df cMUD.exe Controls 4645 +53 TControl.WndProc
00509cc2 +18e cMUD.exe Controls 6342 +33 TWinControl.WndProc
00509894 +034 cMUD.exe Controls 6237 +3 TWinControl.MainWndProc
0047fef8 +014 cMUD.exe Classes 10966 +8 StdWndProc
7c90eae0 +010 ntdll.dll KiUserCallbackDispatcher
77d4e2f2 +044 USER32.dll SendMessageA
009061bc +020 cMUD.exe SciLexer 1601 +2 TScintillaBase.SPerform
00ba8ec1 +009 cMUD.exe ScintillaAddict 407 +0 TScintillaAddict.wmColorize
00505f93 +1df cMUD.exe Controls 4645 +53 TControl.WndProc
00509cc2 +18e cMUD.exe Controls 6342 +33 TWinControl.WndProc
00509894 +034 cMUD.exe Controls 6237 +3 TWinControl.MainWndProc
0047fef8 +014 cMUD.exe Classes 10966 +8 StdWndProc
77d4bcc7 +00a USER32.dll DispatchMessageA
0055f466 +15a cMUD.exe cxControls 961 +45 DragDetect
005621e7 +067 cMUD.exe cxControls 3020 +1 TcxControl.AfterMouseDown
007f1925 +039 cMUD.exe cxInplaceContainer 6868 +2 TcxEditingControl.AfterMouseDown
00561324 +048 cMUD.exe cxControls 2422 +4 DoAfterMouseDown
0056149f +16f cMUD.exe cxControls 2462 +36 TcxControl.WndProc
007f18e2 +01e cMUD.exe cxInplaceContainer 6861 +3 TcxEditingControl.WndProc
00509894 +034 cMUD.exe Controls 6237 +3 TWinControl.MainWndProc
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
00dbbfb8 +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 |
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Sun Oct 28, 2007 3:46 am |
Perhaps you could just not be allowed to delete a module that contains settings? It's easy enough to select them all and MoveTo. Perhaps the "no" option on the popup asking if you want to delete the settings could open MoveTo or something similar?
|
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Mon Oct 29, 2007 9:36 pm |
Well, I'm glad that it was at least hard to get it to crash ;)
Fang's idea is possible, although if it doesn't really crash, then you can just let people move the settings back into a valid module/window.
I want to allow deleting a module/window that has settings...I just need to make sure it's clear that the settings within the module/window will be deleted and not give the option to not delete them. Usually when someone wants to delete a class/module/window they already assume that it's also going to delete the settings inside. |
|
|
|
|
|