Create your own Interactive Fiction

ADRIFT - Interactive Fiction  
Home   |   News ADRIFT News RSS   |   Screenshots   |   Download   |   Games ADRIFT Reviews RSS   |   Forum   |   Help   |   Links
Welcome Guest Register | Login
Popular Games
Pete's Punkin Junkinator
InsideADRIFT #41
All Through the Night
Three Monkeys One Cage
Skybreak v. 1.4
Trick or Treat
The Fortress of Fear
Bug Hunt On Menelaus
Museum Heist
The Day Program
 
Latest Forum Posts
Getting Adrift 4 to ignore "and"
Happy birthday, Rotter
CYS New Year's Prompt contest
Text Adventure Literacy Jam 2026
Merry Christmas!
Short story contest for the forum?
Constellaris Court
Happy birthday reelyor
New Game Uploaded: THINGS THAT GO BUMP IN THE NIGHT
Dominion of Darkness - interactive story of the Dark Lord/Lady
 
Latest Reviews
DRAM 321 Final
Goldilocks is a FOX!
Xanix - Xixon Resurgence
Finn's Big Adventure
Bug Hunt On Menelaus
Magor Investigates...
Classic Adventure
Private Eye
Roozden's Color Code Module
Wumpus Hunt

Make a donation

Cursor  Closing debug window sparately

Issue Type: Status: Priority: Date Submitted: Votes:
Enhancement Open Medium Sat 10th Mar 2012 0 votes Vote Up Vote Down
 
Found in version: Last Updated: Completed in version: Date Completed: Track Changes:
5.0.22 Fri 22nd Feb 2013 Log In
 
P/o PruneSat 10th Mar 2012 09:24
It would be nice if it was possible to close the debug winbdow separately. As it is now it closes when you close the runner.
 
campbellSat 21st Jul 2012 17:54
I'm confused. Would you not want it to close when Runner closes? You can certainly close it on it's own.
 
P/o PruneFri 22nd Feb 2013 12:21
Not necessarily.
Probably just a matter of habbit. But when I use the debugger testing my game, I then close the runner when I have come to the point where things start to go amiss and want to work in the developer. When I do that the debug window closes too. I guess I could just click the developer window up on the screen, but then the runner will still be active in the beackground.
When I have corrected whatever error I've found through the debugger I will still have to run the runner again to check if I've corrected the error.
© 2013 Campbell Wild. All rights reserved. | Contact the Webmaster