Hello i was wondering if there is anyway if i have two monitors i can test the game on one if i find a bug pause the game and code on the other unpause the game and my bug is fixed
Printable View
Hello i was wondering if there is anyway if i have two monitors i can test the game on one if i find a bug pause the game and code on the other unpause the game and my bug is fixed
No.
Hey, who remembers the old "Step-through Editor"? Wasn't it awesome! XD
That nasty thing that paused on every collision/keypress?
Wasn't it maybe first games factory?
Or klik 'n play?
I remember it being a little redundant XD
To return in-topic:
Two monitors yes (extending desktop...)
pause-resume with bugfix no, you'll have anyway to restart the application to see changes take place!
Klik N Play it was, I covered it and some other nostalgic stuff in the March edition of Fused
http://download.clickteam.com/newsletters/march2015.pdf
It came on a series of floppy disks if I remember correctly
I should still have 5 (4?) floppies buried deep in some drawer of my parent's house.
I remember them being light-blue gradient with a white logo.
Even after many reinstall on ever growing machines, they stood fierce against demagnetization <3
They were the substance of which dreams are made XD
Ohhh and the "morphing" effect!
So cute effect I still miss it.
Felt like a small skywalker studio back then X)
Never used in a finished game (and never finished a game, for that matter...) but was so cool!
Is anybody old enough to remember the TRACE and NOTRACE functions for BASIC??
Weeeeee!
Thx for that, tracing - way to make me feel old! :)
I remember something like this when I was first doing HTML - adjust on one monitor and see the changes in the other. Saved tons of time.
But unless someone says otherwise, this is not possible. You could extend the desktop and make two monitors, but you would still need to quit the application and restart to see your changes...
... but holy friggin' cow, what a GREAT IDEA?! I would kill for this feature in 3.0!!
I hope Fusion 3.0 has better options for testing - like real time editing code and also "save states" so you don't need to re-play large areas of a level to test everything.
Closest thing you get is INI dependent testing right now. With my current build there are a few things I can change around in real time but only because rely so much on INIs.
...It's actually the reason WHY I like INIs so much.
Fusion locks the editor when running using "Run application", so you could use "Build & Run" (which will execute externally) and make changes while testing the creation, but as others already said, you won't see these changes until you re-build, re-start.
To help debug events, you could use an edit box / string object and output new lines as your program runs along so you know what's going on.
+1 to DaveC's hope. Me too! Something along the lines of "Step through Events" and "Step over Events" would be great too, so apps can be tested one event at a time and highlight which event is being executed. (Nothing at all like the K&P/TGF1 Step through Editor)