| FBA The Creator http://www.fbacreator.com/fbaforum/ |
|
| debug bug in FBA 0.2.0.135 http://www.fbacreator.com/fbaforum/viewtopic.php?f=2&t=192 |
Page 1 of 1 |
| Author: | Birger [ Sun Jun 07, 2009 9:39 pm ] |
| Post subject: | debug bug in FBA 0.2.0.135 |
Dear evilmajo, hello FBA community.. When tracing through the program, the actual screen output comes 1 frame(loop) to late. The easiest way to recreate: - Load the tutorial project 09b / Gfx Font into the IDE - you should also see/ watch the Stack Dump panel - set a breakpoint at line #23 or somewhere above the statement "count = count + 1" Now we need to follow the code (mentally), watch the app window and the var "count" in the Stack Dump - run the app, Stop: the app window black (o.k.), count == 0 (o.k.) - run the app, Stop: the app window black (hmmh, there should be drawn the countervalue 0), count == 1 (o.K.) - run the app, Stop: the app window shows the digits (hmmh, counter displays 1, but should be 2), count == 2 (o.K.) And I tried to debug the actions in a grid, again, again... Tough Luck, that the grid isn't shown in the Stack Dump. By the way. when the app-window hides my code and I want to move it aside, i first click in the titlebar of the IDE, then in the titlebar of the app and then it can be moved i.e. over the Project Explorer. |
|
| Author: | evilmaio [ Mon Jun 08, 2009 7:10 am ] |
| Post subject: | Re: debug bug in FBA 0.2.0.135 |
Birger, unfortunately that's how the FBA gameloop works  In shorts, you won't see anything on the screen until your mainloop completes: when your mainloop function exits, the screen is redrawn. So if you draw something in the middle of the mainloop and then pause your execution, your window won't be updated until your mainloop completes Regards. |
|
| Author: | Birger [ Mon Jun 08, 2009 12:17 pm ] |
| Post subject: | Re: debug bug in FBA 0.2.0.135 |
Hi evilmajo; yes, as you wrote it should be - I fully agree. o.K., I tried it again  - It's only the first screen, that's missing (when the count should display 0).And - it's NOT unfortunatly how FBA mainloop works It's similiar to a classic automation controller, at framestart the inputs are read, then execution, at the end writing to the outputs. And that's the hit: with FBA you don't need to push a button, therefore the application starts running. Have a nice time. thx Birger |
|
| Author: | Birger [ Mon Jun 08, 2009 8:52 pm ] |
| Post subject: | Re: debug bug in FBA 0.2.0.135 |
jepp again, with another detail, mainloop did draw several times to the screen (the screen is painted), before it stops at a breakpoint. Then the first screen output isn't painted (mainloop was stopped for the second time at that breakpoint). When mainloop has it third stop at same breakpoint, then the screen as drawn after the second stop is painted. |
|
| Author: | Birger [ Thu Jun 11, 2009 11:46 am ] | ||
| Post subject: | Re: debug bug in FBA 0.2.0.135 | ||
How to debug your application seeing the first screen frame output The idea was, to start the app in the IDE, then raise an event and stop the app with reinitialized variables at the breakpoint when the first frame is seen on the screen. It's all written in the attached Source/FBA Project. Don't wonder, I set the projects frame rate to 200.
|
|||
| Page 1 of 1 | All times are UTC |
| Powered by phpBB® Forum Software © phpBB Limited https://www.phpbb.com/ |
|