[Gtkradiant] [Bug 297] New: fixes needed to .pid file check, console logging and preferences reset

gtkradiant@zerowing.idsoftware.com gtkradiant@zerowing.idsoftware.com
Sat, 12 Jan 2002 13:51:12 -0600


http://zerowing.idsoftware.com/bugzilla/show_bug.cgi?id=297

           Summary: fixes needed to .pid file check, console logging and
                    preferences reset
           Product: GtkRadiant
           Version: 1.2-nightly
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: editor
        AssignedTo: ttimo@idsoftware.com
        ReportedBy: ttimo@idsoftware.com


<TTimo> what is still broken though, is the preferences reset, the console 
logging and the .pid stuff 
<TTimo> because of the changes in the startup procedure 
<EvilTypeGuy> What's wrong with console logging?
<TTimo> this is going to make things difficult to debug when people report 
problems 
<EvilTypeGuy> is that a prefs thing too?
<TTimo> well we often log the console to get people to send that back to us for 
debugging 
<TTimo> it is also useful to debug what happens when the editor starts and 
there is no console yet 
<leaf> okay, TTimo.
<TTimo> right now the console logging actually starts after the game selection 
is done 
<EvilTypeGuy> Ah....
<TTimo> means we are missing the critical new code that loads globals prefs, 
parses .game files and does the UI prompt 
<TTimo> the othe related thing is .pid checking 
<TTimo> we use a .pid file to catch when an editor startup failed 
<EvilTypeGuy> ya, I noticed it was kinda screwy
<TTimo> i.e. if it crashed or went to a fatal error before the user can get to 
interactive mode 
<TTimo> we need to have that .pid file working at global level (right now it 
happens 'after' game select) 
<TTimo> and also, if error happens during startup / game select, we prompt for 
editing preferences .. which will crash since we don't have any prefs in this 
state 
<TTimo> I think I'll stick that in a new bug report



------- You are receiving this mail because: -------
Whoops!  I have no idea!