Hello Peter!

Replying to a message of Peter Fitzsimmons to Julien Pierre:

 JP>> I'm currently trying to write to the screen directly  using Vio calls
 JP>> (VioSetPhysBuf and the like) ..

 PF> Is this a text mode, or graphics app?  If text mode,  don't use the
 PF> physical buffer.  Use the LVB (VioGetBuf),  or better yet, straight
 PF> VioWrt...() calls.  These are damn fast if used correctly.

Well, thank you, but it's a full screen graphical app.

 JP>> you cannot type ALT-ESC to go back to  the debugger !!!!!! Probably
 JP>> the "VioScrLock" worked

 PF> Exactly --- because VioScrLock() is doing what you asked it to.  You
 PF> can't have your cake and eat it too.  This same problem would occur
 PF> even if you were using a non-pm debugger.   

Yeah, I finally figured it out myself in the meantime :-) The problem is
that my message took a week to reach you, and the answer one more week :-(
Maybe we could establish an interzone fidonet link ?

 PF> You should only ever have the screen locked for a moment or two.  It
 PF> is usually not a problem to place a breakpoint outside of the
 PF> lock/unlock,since you're not supposed to be doing much in there
 PF> anyway. Just lock,draw, unlock, in quick succession.

That's what I will probably do ... But still there is a problem : how can I
make my application run in the background ? A "solution" is not
to lock the screen, but then there is corruption when switching :-( Do you
have an idea ?
The reason I want to do that is because I am going to develop a game with
music and I don't want it to stop .. Do I have to play the music in a
separate thread ?
Another question : is it possible to use MMPM/2 to play the music if the
application is not PM (in this case, full screen graphic) ?

Bye, Julien!

--- FleetStreet 0.87wb