Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warning screen should always be enabled or at the very minimum togglable #314

Open
barbudreadmon opened this issue Jun 23, 2022 · 8 comments

Comments

@barbudreadmon
Copy link

barbudreadmon commented Jun 23, 2022

Warning screen is an important feature of MAME, among other things it allows the user to know if a game is playable, which is primordial information if you don't want to waste your time desperately trying to launch a game that simply doesn't work.

For some weird reason, this important feature is disabled in the libretro port, and it doesn't seem there is any way to enable it. I think it has to do with the following code :

#if defined(EMSCRIPTEN) || defined(__LIBRETRO__)
// also disable for the JavaScript port since the startup screens do not run asynchronously
show_gameinfo = show_warnings = false;
#endif

@riggles1
Copy link

Wouldn't be bad, sure the info is in the mame menu as well, but it helps newcomers from asking unnecessary things.

As long as we can set:
skip_gameinfo 1
skip_warnings 1

in the RA root folder/mame.ini file for us who set the core to read additional settings from the .ini.

@Tasosgemah
Copy link

Optional, sure. "Always" nope.

@ghost
Copy link

ghost commented Oct 11, 2022

Just for the record the code has not been disabled anywhere. It not settings based why its not happening this one does need looked into.

@ghost
Copy link

ghost commented Oct 28, 2022

There is nothing that can be done without hacking code up and is desirable to stay upstream. If they fix the EMSCRIPTEN port we can implement them fixes here.

@barbudreadmon
Copy link
Author

barbudreadmon commented Oct 28, 2022

There is nothing that can be done without hacking code up and is desirable to stay upstream

The code is already hacked... It is because it is hacked that this message isn't shown anymore...

If they fix the EMSCRIPTEN port

Seriously ? Are you trolling intentionally ?

@ghost
Copy link

ghost commented Oct 29, 2022

sorry but its the same upstream for the same reason look here.

https://github.com/mamedev/mame/blob/aefb991c77462a867f6cd3d16fe912374cc8772e/src/frontend/mame/ui/ui.cpp#L422-L425

This is ra limitations the way its run model works sorry if you dont like the really of the matter. The main point to take from this is no one has intentionally disabled them which was unclear at the start of the topic.

@barbudreadmon
Copy link
Author

barbudreadmon commented Oct 29, 2022

sorry but its the same upstream for the same reason look here.

This is not emscripten here, this is the libretro project.
This message existed in earlier versions of this core.
This message still exists in some vintaged mame cores, and can be toggled through core options.
It was intentionally disabled by someone, this decision was even criticized by the mame team for legit reasons.

Saying it will be restored when emscripten will be fixed (meaning never), while the 2 things are totally unrelated, is yet another non-sense.

@ghost
Copy link

ghost commented Oct 29, 2022

Well it is open source if you or anyone else want to put a pull request in feel free or anyone else can. Im giving you a legitimate why they arent there. If you feel strongly contract the mame team about the emscripten port not having the info screens. I dont know what to say to you beyond that. I wont get drawn into your baseless accusations, if you disable that define mame simply wont start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants