On-screen info during emulation about mupen64plus HOT 13 CLOSED

We could always look into modifying our screen output after updateScreen(), 
drawing
over it.

Me and nmn have started adding this into the plugin for Rice Video, please read 
the
specs on how it works...

I'm glad you two are working on this change, but committing broken or 
incomplete code
into trunk is a sure fire way to get your trunk commit privileges revoked. For a
feature like this, you need to have Richard42 create a branch for you to work 
in.
Committing code that breaks trunk makes it difficult for others to develop.

Given the spaghetti code that is Rice and my recent widescreen code as an 
example, 
I also suggest a branch. That said, I'd love to see this so good luck. :)

nmn, when I try to compile our branch I get the following:
In file included from stdafx.h:40,
                 from OGLGraphicsContext.cpp:19:
Video.h:23:25: error: OGLFreeType.h: No such file or directory
Video.h:24: error: expected initializer before ‘*’ token
make: *** [OGLGraphicsContext.o] Error 1

Did you forget to commit a file or am I doing it wrong?

I forgot to commit the files. They should be in now...

Yeah, sorry about putting this in the trunk. I didn't realize how hackish it was
until I had a second look. (Not to mention it didn't compile because of the 
missing
files.)

I am now relying on this to be done for ReRecording. I really need a way to 
output
things to the screen.

I think I can help you out with this one, but issue 35 and issue 8 are queued 
ahead
of it.

Alright, OSD support should be working in it's branch. If anyone could help 
test for
regressions and such that would be helpful.

Hey, I tried to test this but after switching to the branch, nothing seems to 
output to the screen via the OSD. What events trigger messages? Or are we not 
there 
yet. 

It's not working yet.  I did some code rearranging locally and looked at it 
pretty
hard but it's still not correct on my main PC.  I'm going to commit my changes
tonight and try on a different machine.  The glBitmap call in OGLFT seems to be 
doing
something strange.

This feature was merged into trunk in r452.