mirror of
https://github.com/dolphin-emu/dolphin.git
synced 2025-07-23 06:09:50 -06:00
Eliminate SettingsHandler's SetBytes
and Reset
methods
Also make the `Decrypt` method private. As far as I can tell, the only motivation for exposing the `SetBytes` and `Reset` methods is to allow `CBoot::SetupWiiMemory` to use the same `SettingsHandler` instance to read settings data and then write it back. It seems cleaner to just use two separate instances, and require a given `SettingsHandler` instance to be used for either writing data to a buffer or reading data from a buffer, but not both. A natural next step is to split the `SettingsHandler` class into two classes, one for writing data and one for reading data. I've deferred that change for a future PR.
This commit is contained in:
@ -75,35 +75,11 @@ TEST(SettingsHandlerTest, DecryptMultipleSettings)
|
||||
EXPECT_EQ(handler.GetValue("foo"), "bar");
|
||||
}
|
||||
|
||||
TEST(SettingsHandlerTest, SetBytesOverwritesExistingBuffer)
|
||||
{
|
||||
Common::SettingsHandler handler(BUFFER_A);
|
||||
ASSERT_EQ(handler.GetValue("key"), "val");
|
||||
ASSERT_EQ(handler.GetValue("foo"), "");
|
||||
|
||||
handler.SetBytes(BUFFER_B);
|
||||
EXPECT_EQ(handler.GetValue("foo"), "bar");
|
||||
EXPECT_EQ(handler.GetValue("key"), "");
|
||||
}
|
||||
|
||||
TEST(SettingsHandlerTest, GetValueOnSameInstance)
|
||||
{
|
||||
Common::SettingsHandler handler;
|
||||
handler.AddSetting("key", "val");
|
||||
EXPECT_EQ(handler.GetValue("key"), "");
|
||||
|
||||
Common::SettingsHandler::Buffer buffer = handler.GetBytes();
|
||||
handler.SetBytes(buffer);
|
||||
EXPECT_EQ(handler.GetValue("key"), "val");
|
||||
}
|
||||
|
||||
TEST(SettingsHandlerTest, GetValueAfterReset)
|
||||
{
|
||||
Common::SettingsHandler handler(BUFFER_A);
|
||||
ASSERT_EQ(handler.GetValue("key"), "val");
|
||||
|
||||
handler.Reset();
|
||||
EXPECT_EQ(handler.GetValue("key"), "");
|
||||
}
|
||||
|
||||
TEST(SettingsHandlerTest, EncryptAddsLFOnNullChar)
|
||||
|
Reference in New Issue
Block a user