Dude, it appears on the screen for like 2 frickin seconds, whats so distracting about that, unless you're impatient and time moves really slow cause this is getting on my nerves
, it cant be disabled so lets move on please
(08-19-2011, 04:48 AM)Blaze X Wrote: [ -> ]Dude, it appears on the screen for like 2 frickin seconds, whats so distracting about that, unless you're impatient and time moves really slow cause this is getting on my nerves, it cant be disabled so lets move on please
Two seconds is long enough to distract my eyes and to take me out of the game. Why do you care? The point is that it bothers me and clearly it bothers others if other threads have been started on the topic before. Just because you don't care about it doesn't mean I should have to feel the way you do.
Find another thread if this topic is getting on your nerves. It doesn't concern you and adding the option wouldn't affect you. Why are you even commenting?
(08-19-2011, 05:16 AM)chinagreenelvis Wrote: [ -> ] (08-19-2011, 04:48 AM)Blaze X Wrote: [ -> ]Dude, it appears on the screen for like 2 frickin seconds, whats so distracting about that, unless you're impatient and time moves really slow cause this is getting on my nerves, it cant be disabled so lets move on please
Two seconds is long enough to distract my eyes and to take me out of the game. Why do you care? The point is that it bothers me and clearly it bothers others if other threads have been started on the topic before. Just because you don't care about it doesn't mean I should have to feel the way you do.
Find another thread if this topic is getting on your nerves. It doesn't concern you and adding the option wouldn't affect you. Why are you even commenting?
He's only saying what he feels as you do and you're both right. I suggest you to launch a poll on this subject it could be interesting
Nah really, I don't want to have the forum even more cluttered with more useless polls >_>
I've fixed the problem for myself, but it involves editing the sourcecode and then building using the instructions found here:
http://code.google.com/p/dolphin-emu/wiki/Windows_Build
In Visual Studio, use the Solution Explorer to find
Core > HW (Flipper/Hollywood > EXI - Expansion Interface > EXI_DeviceMemoryCard.cpp
The following lines can be commented out:
Code:
//INFO_LOG(EXPANSIONINTERFACE, "Reading memory card %s", m_strFilename.c_str());
Code:
//Core::DisplayMessage(StringFromFormat("Wrote memory card %c contents to %s",
//data->memcardIndex ? 'B' : 'A', data->filename.c_str()).c_str(), 4000);
Code:
//Core::DisplayMessage(StringFromFormat("Writing to memory card %c", card_index ? 'B' : 'A'), 1000);
This will remove the memory read/write nags.
.. "Proper" fix would be to change Source/Core/Core/Src/Core.cpp at
Quote:void DisplayMessage(const char *message, int time_in_ms)
{
SCoreStartupParameter& _CoreParameter =
SConfig::GetInstance().m_LocalCoreStartupParameter;
g_video_backend->Video_AddMessage(message, time_in_ms);
if (_CoreParameter.bRenderToMain &&
SConfig::GetInstance().m_InterfaceStatusbar) {
Host_UpdateStatusBar(message);
} else
Host_UpdateTitle(message);
}
to
Quote:void DisplayMessage(const char *message, int time_in_ms)
{
SCoreStartupParameter& _CoreParameter =
SConfig::GetInstance().m_LocalCoreStartupParameter;
// TODO: if ( some_config_var)
return;
g_video_backend->Video_AddMessage(message, time_in_ms);
if (_CoreParameter.bRenderToMain &&
SConfig::GetInstance().m_InterfaceStatusbar) {
Host_UpdateStatusBar(message);
} else
Host_UpdateTitle(message);
}
Nice! That is indeed much simpler and paves the way for a toggle.