Chest export Export fails immediatly on latest version

[neilwils]

Crash Log 11/9/2024 - 12:15 PM: The added or subtracted value results in an un-representable DateTime. Parameter name: value at System.DateTime.AddTicks(Int64 value) at TBChestTracker.ExportWindow.Window_Loaded(Object sender, RoutedEventArgs e) in C:\Users\SICGames\Documents\Visual Studio Projects\TBChestTracker\TBChestTracker\ExportWindow.xaml.cs:line 136 at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent) at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root) at MS.Internal.LoadedOrUnloadedOperation.DoWork() at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks() at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget) at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget) at System.Windows.Interop.HwndTarget.OnResize() at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.HwndSubclass.DefWndProcWrapper(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

[SICGames]

send me clanchests.db file through email. sicgames88@gmail.com the file is located in your document's folder\TotalBattleChestTracker\db

[SICGames]

it's not parsing first date entry key and last date key entry correctly. It may be returning false on attempting to parse and continuing thinking everything's okay. It's upon the export dialog loading that it's trying to build the from date and to date's blacked out dates.

[SICGames]

In RC 2.2 it safely handles this exception.

[gregenspurger]

If you click at custom range calendar at startdate it jumps always to JULY (11.7.2024) ENDDATE is OK. Maybe that is the Problem.

[gregenspurger]

Mismatch 7.11. and 11.7. Enddate is OK

[gregenspurger]

clanchests.zip

[SICGames]

is this German? mm.dd.yyyy format? Because newest update doesn't enforce en-US localization, it causes a bit of a hiccup. I don't think there's a way to convert en-US date format to de-DE or at least detect what type of date format localization it is. Not that I know of. When you continued to count, it saw that 11/11/24 didn't match 11.11.24 and added a new entry inside clanchests.db. Open the clanchests.db file and convert the / into a . search and replace would be much easier. In the future, i'll have possibly make a way to detect what locale the datetime is using and fix it accordingly.

On Mon, Nov 11, 2024 at 8:24 AM gregenspurger @.***> wrote:

clanchests.zip https://github.com/user-attachments/files/17703001/clanchests.zip

— Reply to this email directly, view it on GitHub https://github.com/SICGames/TBChestTracker/issues/92#issuecomment-2468172426, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAZ6JSPBXCVW2B5BKCA5PD2ACVZ7AVCNFSM6AAAAABRQLCDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGE3TENBSGY . You are receiving this because you commented.Message ID: @.***>

[gregenspurger]

Thanks, yes PC is on German language, TotalBattle on English language. GERMAN Date format is dd.mm.yyyy Till yesterday it was all OK ( i jumped from version 2.0.0. RC 2.1 to 2.0.0 RC 2.3

Thank for your Work!

Am 12.11.2024 um 05:09 schrieb Paul @.***>:

is this German? mm.dd.yyyy format? Because newest update doesn't enforce en-US localization, it causes a bit of a hiccup. I don't think there's a way to convert en-US date format to de-DE or at least detect what type of date format localization it is. Not that I know of. When you continued to count, it saw that 11/11/24 didn't match 11.11.24 and added a new entry inside clanchests.db. Open the clanchests.db file and convert the / into a . search and replace would be much easier. In the future, i'll have possibly make a way to detect what locale the datetime is using and fix it accordingly.

On Mon, Nov 11, 2024 at 8:24 AM gregenspurger @.***> wrote:

clanchests.zip https://github.com/user-attachments/files/17703001/clanchests.zip

— Reply to this email directly, view it on GitHub https://github.com/SICGames/TBChestTracker/issues/92#issuecomment-2468172426, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAZ6JSPBXCVW2B5BKCA5PD2ACVZ7AVCNFSM6AAAAABRQLCDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGE3TENBSGY . You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/SICGames/TBChestTracker/issues/92#issuecomment-2469551506, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFKPVAVOHGDYRWB3QMYQV32AF5QFAVCNFSM6AAAAABRQLCDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRZGU2TCNJQGY. You are receiving this because you commented.

Mit freundlichen Grüßen Gerhard Regenspurger

---

Gerhard Regenspurger, Rossau 154, 2020 Aspersdorf - AUSTRIA mobil: +43 (0)664 / 432 33 31 e-mail: @.***

[gregenspurger]

i played around with the clanchest.db The OLD and GOOD entrys are like: "11/12/2024" format is mm/dd/yyyy The new and NOT working entrys are: "12.11.2024" format is now dd/mm/yyyy ONLY if I change 12.11.2024 to 11/12/2024 it WORKS. Conclusion: Not only "." is the Problem and changing to "/" doesn't help. I must also correct the DATEFORMAT from dd/mm/yyyy TO mm/dd/yyyy

I hope this helps!

[SICGames]

the RC 2.4 version does this for you automatically. It'll alert you if there is a invalid date format. If it doesn't, run Validate Clan Chest Data Integrity first.

On Tue, Nov 12, 2024 at 2:38 PM gregenspurger @.***> wrote:

i played around with the clanchest.db The OLD and GOOD entrys are like: "11/12/2024" format is mm/dd/yyyy The new and NOT working entrys are: "12.11.2024" format is now dd /mm/yyyy ONLY if I change 12.11.2024 to 11/12/2024 it WORKS. Conclusion: Not only "." is the Problem and changing to "/" doesn't help. I must also correct the DATEFORMAT from dd/mm/yyyy TO mm/dd/yyyy

I hope this helps!

— Reply to this email directly, view it on GitHub https://github.com/SICGames/TBChestTracker/issues/92#issuecomment-2471408457, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACAZ6JVPBDEX233IYSU7VUL2AJKJTAVCNFSM6AAAAABRQLCDWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZRGQYDQNBVG4 . You are receiving this because you commented.Message ID: @.***>