On-screen info during emulation

[GoogleCodeExporter]

Seems like it would be useful to be able to provide information to the user
inside the emulator window. For example, when a user changes the current
statesave slot, "Statesave Slot X" would appear briefly on the screen,
where X is the slot number.

It would be nice if this could be kept plugin-independent, but I'm not sure
if that's possible.

Original issue reported on code.google.com by ebenbl...@gmail.com on 24 Mar 2008 at 10:45

[GoogleCodeExporter]

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

Original comment by sgorman07@gmail.com on 14 Apr 2008 at 4:46

[GoogleCodeExporter]

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

Original comment by sgorman07@gmail.com on 22 Apr 2008 at 5:37

• Changed state: Started

[GoogleCodeExporter]

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.

Original comment by ebenbl...@gmail.com on 22 Apr 2008 at 6:13

[GoogleCodeExporter]

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. :)

Original comment by sknau...@wesleyan.edu on 23 Apr 2008 at 1:33

[GoogleCodeExporter]

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?

Original comment by sgorman07@gmail.com on 23 Apr 2008 at 8:22

[GoogleCodeExporter]

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.)

Original comment by NmnNotmy...@gmail.com on 23 Apr 2008 at 7:18

[GoogleCodeExporter]

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

Original comment by sgorman07@gmail.com on 25 Apr 2008 at 11:03

[GoogleCodeExporter]

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

Original comment by ebenbl...@gmail.com on 25 Apr 2008 at 2:12

[GoogleCodeExporter]

Original comment by ebenbl...@gmail.com on 26 Apr 2008 at 1:06

[GoogleCodeExporter]

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

Original comment by NmnNotmy...@gmail.com on 27 Apr 2008 at 7:15

[GoogleCodeExporter]

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. 

Original comment by sknau...@wesleyan.edu on 9 May 2008 at 12:38

[GoogleCodeExporter]

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.

Original comment by richard...@gmail.com on 9 May 2008 at 12:49

[GoogleCodeExporter]

This feature was merged into trunk in r452.

Original comment by ebenbl...@gmail.com on 16 May 2008 at 5:52

• Changed state: Fixed