The problem is that, Hungarian uses "yyyy. MMMM d." for long date format while "history.txt" uses "dd.mm.yy", i have fixed the year problem by adding the century before pass the date to the VB6 function FormatDateTime, but it seems that function doesn't distinguish between day and month if the day is <= 12
I wrote it this afternoon in VB2010 and works fine there, it should work with other regional settings too... (maybe there's a much simpler way, however it was the one which came into my mind )
Private Function GetCorrectDate(ByVal Input As String, ByVal Format As DateFormat) As String
Dim DateArray() As String = Split(Input, ".")
' Fix the year tag
If (DateArray(2) > 92) And (DateArray(2) < 99) Then
DateArray(2) = "19" + DateArray(2)
ElseIf DateArray(2) < 1992 Then
DateArray(2) = "20" + DateArray(2)
End If
Dim RealDate As New Date(DateArray(2), DateArray(1), DateArray(0))
Return FormatDateTime(RealDate, Format)
End Function
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
LabelDate.Text = GetCorrectDate(TextBox1.Text, DateFormat.LongDate)
End Sub
Private Function GetCorrectDate(ByVal Input As String, ByVal Format As DateFormat) As String
Dim DateArray() As String = Split(Input, ".")
Return FormatDateTime(DateSerial(DateArray(2), DateArray(1), DateArray(0)), Format)
End Function
Bug:
If there are no items with [+] for a certain version (for example TC 7.56a final) and filtering for [+] is enabled, I got an error "Runtimeerror 35600: Index boundaries ...".
I think you do not handle zero sized lists correctly.
Suggestions:
* Introduce a column with version (beside date) when feature was introduced/bug was fixed. With this you can easily identify for example in a [+]-filtered list, when this feature was introduced ....
* Make columns sortable- especially helpful for date column ...
If there are no items with [+] for a certain version (for example TC 7.56a final) and filtering for [+] is enabled, I got an error "Runtimeerror 35600: Index boundaries
Confirmed.
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14 TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Fixed: Error occurs if the changes list is empty after applying filter.
hoppfrosch wrote:* Introduce a column with version (beside date) when feature was introduced/bug was fixed. With this you can easily identify for example in a [+]-filtered list, when this feature was introduced ....
The first line in the list always show the version number even when it is filtered, but this was broken in beta 3
hoppfrosch wrote:* Make columns sortable- especially helpful for date column ...
ts4242 wrote:
The first line in the list always show the version number even when it is filtered, but this was broken in beta 3
Not quite true: if you select the version "all" to display - you cannot identify in which version the feature was introduced/bug was fixed. Therefore my suggestion for version column ... Might be nice also to see the version of currently selected line in the status bat as well ...
ts4242 wrote:
hoppfrosch wrote:* Make columns sortable- especially helpful for date column ...
It is already sorted by date in the history file
You're right - no really need to sort for other columns than date (which "corresponds with version" - each date belongs to a dedicated version). If the list is always sorted by date ... the order is clear. But if you want to sort in "real chronological order" instead of reverse chronological order, a sort possibility might be useful anyway.
One more idea/feature request:
Introduction of a "Quick Search" feature: Typing for example "USB" filters out all lines containig "USB" on the fly ...
The beta5 does not show any changes on my system, whereas the beta4 works fine. Only the tree of versions is shown, and it does not matter if I select All changes, Additions or Fixes.
Odd, after first loading the TC8beta8 history file and afterwards the beta9 file everything works now.
Maybe an ini setting that caused a quirk. Well, ignore my earlier report then, problem seems to be solved.
)
