Home Page Forums MAME MAME MAME startup sequence nitpick

Stop? Why?

That was just an anecdote, and isn't even being close to being the topic of this thread.

Please let's not have this devolve in another shouting match.

Eocene was citing that he *had* solved the problem outside of the scope of MAME to his satisfaction.

Right on queue: arbee's sarcastic contribution.

Well, that's the last time I'll defend you then.

Lol, you're right - I misread.
Nono, by all means please continue defending me.

If "fuck it, let an external frontend handle it, if any" is a solution, then let's just remove all the internal UI then. Seems about fair.

No, that's how he solved it for himself. I don't think he'd claim it was a universal thing.

Well could Mame show the MAME logo on startup (with the initializing info underneath)

and when starting a machine could the cabinet image not be shown as it was starting up.

Then the (don't tell us this machine is not working as we bloody well know it's not working , we wrote it (red message) could appear over the top of this)

progress bars could be added and/or info on what mame is loading or checking for just to inform people that it has not crashed.

just things other software does when starting up.

as for external front-ends???

... or you could not do any of those things

and simply output status messages to sdout

What you could do, and would have a chance to be accepted, is to create a communicate-with-frontend protocol through stdin/out activated with a command line option. Then you'd change the code to encode the rom check/loading/etc information so that the frontend can easily parse and display it in whichever way it wants.

If you're funky you can even try to pass the window handle from the frontend to mame through that protocol (os-dependent obviously, would work under linux, dunno windows or osx) to avoid window transitions.

But you'll have to do it cleanly if you want to have a chance to have it accepted, obviously.

OG.