From 5ecb89eeec29bac39de1b44427bf687adb1f50b1 Mon Sep 17 00:00:00 2001 From: cantabile Date: Tue, 24 Jul 2012 02:39:37 +0000 Subject: [PATCH] Shift times: Use TimeEdit::SetTime() instead of TimeEdit::SetValue() TimeEdit::SetValue() will trigger TimeEdit::OnModified(), but that doesn't always update the internal "time" property. TimeEdit::OnModified() seems to be designed to handle editing the value with the keyboard, not with SetValue(). Originally committed to SVN as r6943. --- aegisub/src/dialog_shift_times.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aegisub/src/dialog_shift_times.cpp b/aegisub/src/dialog_shift_times.cpp index 170e10dc0..3148e9f9e 100644 --- a/aegisub/src/dialog_shift_times.cpp +++ b/aegisub/src/dialog_shift_times.cpp @@ -260,7 +260,7 @@ void DialogShiftTimes::OnHistoryClick(wxCommandEvent &evt) { json::Object& obj = (*history)[entry]; if (obj["is by time"]) { - shift_time->SetValue(lagi_wxString(obj["amount"])); + shift_time->SetTime(AssTime(lagi_wxString(obj["amount"]))); shift_by_time->SetValue(true); OnByTime(evt); }