Changelogs

Overview

These changelogs reflect the history of all files in the Subversion repository. The changelog has been generated at 2016-05-09 08:38:04

Select Changelog:

FileZilla 3, FileZilla Server,
Legacy FileZilla 2, Legay FileZilla Server

Select page:

[] [1 14 26 39 40 41 42 43 264 484 705] []

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

2013-05-13 01:04 VZ, revision 73973

Whack-a-mole with wxOSX/PPC unit tests continued. The problem was not related to float-to-double conversions in wxAny code, try to narrow it even further.

2013-05-13 01:04 VZ, revision 73972

Fix harmless Clang warning about unreachable code. Unfortunately Clang intelligent flow analysis prevents us from using different asserts for invalid parameter value and unhandled one, which could happen if more elements are added to wxMouseButton enum in the future. Closes #15201.

2013-05-12 22:34 VZ, revision 73971

Disable double-to-float conversion tests in wxAny code. This seems to be the reason for the heap corruption in wxOSX PPC builds.

2013-05-12 22:34 VZ, revision 73970

Disable the rest of Editable() test for wxBitmapComboBox. See r73957, this test keeps failing when running on a build slave, even though it passes when ran locally.

2013-05-12 22:34 VZ, revision 73969

Use "-t" option when running buildbot tests under Windows. Use "-t" in runtests.bar used by Windows build slaves to get more information about the test failures, notably if they crash before completing.

2013-05-12 22:34 VZ, revision 73968

Fix spurious g++ warning about possibly uninitialized variable use. The variables are actually initialized in all cases if the enum has valid value but the compiler doesn't seem to take this into account, so just initialize them always to avoid the warnings.

2013-05-12 22:18 SC, revision 73967

deactivating r65382 see #12267 (which does not seem to happen anymore even without this change), fixes #14938,

2013-05-12 21:19 VZ, revision 73966

Enable another test in wxAnyTestCase under OS X.

2013-05-12 21:19 VZ, revision 73965

Recognize "sandbox" user as indicating automatic testing. The buildbot slaves actually use "sandbox" as the user name, not "buildbot", so test for the former instead for the latter, see r73963.

2013-05-10 21:21 VZ, revision 73964

Enable yet more tests in wxAnyTestCase::GetAs(). This is part of the continuing series of commits to find out what results in heap corruption in wxOSX PPC builds.

2013-05-10 21:21 VZ, revision 73963

Recognize "buildbot" user in IsAutomaticTest() too. Some build slaves apparently run under "buildbot" user and not "buildslave", recognize them as running automatic tests too. Also show the name of the current system and user on startup to avoid such guess work in the future.

2013-05-10 21:21 VZ, revision 73962

Revert "Show the name of the actually tested class in text entry unit tests." Revert r73959, the name of the control can be seen from the name of the failing test case actually, so there is no need to include it in the message.

2013-05-10 20:31 SC, revision 73961

applying editor part of patch, see #15003

2013-05-10 15:25 VZ, revision 73960

Use wxjpeg_boolean in libtiff sources. This fixes compilation problem when using libtiff with the built-in modified version of libjpeg that uses wxjpeg_boolean instead of boolean as it doesn't define boolean at all in its headers, but just wxjpeg_boolean. Closes #15179.

2013-05-10 15:22 VZ, revision 73959

Show the name of the actually tested class in text entry unit tests. This test is used for several different classes, show the name of the class being tested when the assert in Editable() test fails.

2013-05-10 15:22 VZ, revision 73958

Enable a few more tests in wxAnyTestCase::GetAs(). This is part of the continuing series of commits to find out what results in heap corruption in wxOSX PPC builds.

2013-05-10 01:22 VZ, revision 73957

Disable a sporadically failing check in wxBitmapComboBox unit test. This check keeps failing in buildbot builds even though it always passes in local ones (and sometimes in buildbot ones too). Disable it to allow the entire test suite to pass.

2013-05-10 01:22 VZ, revision 73956

Reduce the number of wxAny tests ran under wxOSX further. Something in GetAs() test definitely corrupts memory, but what?

2013-05-10 00:29 VZ, revision 73955

Start bisecting GetAs() wxAny test itself. This is the test that results in memory corruption in wxOSX PPC builds, try to find out where exactly does this happen.

2013-05-09 21:56 VZ, revision 73954

Leave only a single wxAny unit test disabled. It looks like the culprit is GetAs() test, verify it.

2013-05-09 01:18 VZ, revision 73953

Another attempt to isolate memory corrupting wxAny test. We now know it's either As() or GetAs() (or both).

2013-05-09 00:01 VZ, revision 73952

Continue bisecting tests crash in PPC OS X builds. Disable more wxAny tests.

2013-05-09 00:00 VZ, revision 73951

Fix wxRichTextCtrl test compilation. Work around broken pre-C++98 for loop scoping rules in VC6. See #15184.

2013-05-08 23:17 VZ, revision 73950

Really disable wxAny tests under wxOSX. Instead of disabling them everywhere but there. See r73944.

2013-05-08 13:21 VZ, revision 73949

Fix duplicate wxContextMenuEvent generation in wxMSW. Prevent WM_CONTEXTMENU from being propagated upwards the window parent chain by DefWindowProc(), we already do it ourselves and not marking the message as processed could result in multiple calls to the same wxEVT_CONTEXT_MENU handler if it skipped the event. See #13683.

2013-05-08 13:21 VZ, revision 73948

Fix wrong wxUSE_ACCEL around wxUSE_HOTKEY-related code in wxMSW. Closes #15193.

2013-05-08 13:21 VZ, revision 73947

Add wxVector<>::const_reverse_iterator. Provide this type too for compatibility with std::vector<>. Closes #15192.

2013-05-07 23:09 RD, revision 73946

Call InitializeModules instead of just module->Init(). This is needed so the module will have the proper state and not cause an assert when the modules are cleaned up. Since InitializeModules will skip any that are already initialized it doesn't hurt to call it for modules loaded later.

2013-05-07 17:56 VZ, revision 73945

Test for NULL associated frame in doc/view event handling code. A view might not have any associated frame at all (this is probably a bad idea but we don't seem to explicitly forbid this). This should have been part of r73943, see #14314.

2013-05-07 17:10 VZ, revision 73944

Disable more wxAny tests under OS X to try to find the buildbot crash. Disabling wxVariantConversions test was not enough to fix the crash happening in OS X PPC build slave, so disable a few more of them. Temporarily do it for any wxOSX build, the run-time check for buildbot will be restored later when I finally manage to find the problematic test(s?).

2013-05-07 17:07 VZ, revision 73943

Fix for event propagation in "single document" doc/view mode. Ensure that the events still get to wxDocManager even when we are using the single document mode in which a view can be directly associated with the parent frame. Closes #14314.

2013-05-06 23:46 VZ, revision 73942

Disable wxAny-to-wxVariant conversion test case under OS X. This is a blind attempt to fix the test crash under PPC OS X.

2013-05-06 15:39 JS, revision 73941

Applied patches for #15184 (wxRichTextAction fix for when the command identifier is wxRICHTEXT_CHANGE_OBJECT) and #15185 (Make adding/deleting wxRichTextTable rows and columns undoable)

2013-05-06 15:08 VZ, revision 73940

Fix a typo in wxNumberFormatter styles documentation. s/cab/can/

2013-05-06 10:54 JS, revision 73939

Applied patch #15183 (wxRichTextTable::DeleteColumns doesn't remove the deleted columns: dghart)

2013-05-06 02:31 VZ, revision 73938

Add IEEE 754 single/double precision support to wxDataStream classes. Allow to optionally raed/write float/double values in IEEE 754 single/double precision formats, respectively, instead of always using the extended precision format for both of them. This makes the code more flexible, allowing for better interoperability with the other programs, and also allows to implement floating point functions in these classes even when wxUSE_APPLE_IEEE is turned off (as can be the case because of the licencing concerns for the code in extended.c). Closes #10625.

2013-05-06 02:30 VZ, revision 73937

Minor wording fixes in wxDataStream classes documentation. Mostly just s/amount/number/

2013-05-06 02:30 VZ, revision 73936

Test wxDataStream floating point methods in big endian format too. Added a hack to test float/double reading/writing using wxDataInputStream/wxDataOutputStream to the test case using big endian extended float format too.

2013-05-06 02:30 VZ, revision 73935

No changes, just a small optimization in DataStreamTestCase. Don't create streams on the heap completely unnecessarily, just allocate them on the stack. This makes the code shorter, safer and slightly more efficient.

2013-05-06 02:30 VZ, revision 73934

No real changes, just rename double variables to "d". Don't use "i" or "f" for double variable names, this is confusing, especially when we do it inconsistently. See #10625.

2013-05-06 02:30 VZ, revision 73933

Extract common parts of wxData{In,Out}putStream in a common base class. No real changes, just put BigEndianOrdered() and SetConv() methods and the corresponding fields in a common wxDataStreamBase class instead of duplicating them in wxDataInputStream and wxDataOutputStream. This will make it simpler to add more features common to both classes in the future, see #10625.

2013-05-05 18:17 VZ, revision 73932

Don't use gtk_file_chooser_set_filename() for save file dialogs. This seems to be broken in old GTK+ versions, so use gtk_file_chooser_set_current_name() and gtk_file_chooser_set_current_folder() for save file dialogs which seem to work in all versions. Closes #15133.

2013-05-05 13:48 SJL, revision 73931

Speculative fix for wxWebView unit tests on OSX. Use stringByEvaluatingJavaScriptFromString as it is guaranteed to return an NSString.

2013-05-05 02:07 VZ, revision 73930

Correct misleading error message in locale mismatch assert. Don't advise people to use non-existent (or at least not publicly accessible) wxSetLocale(), they should just create wxLocale objects instead.

2013-05-05 02:00 VZ, revision 73929

Use wxWindow::Refresh() instead of artificial wxPaintEvent in the test. This fixes memory leaks under wxMSW: as the test code didn't (and couldn't) call wxPaintDCImpl::EndPaint(), there was a leak for each wxPaintEvent generated in it since the changes to wxDC caching in r72938. It's also preferable because it uses public API instead of feeding events to the window which is not documented to work. Unfortunately even using Refresh() still doesn't allow the test to work under wxOSX.

2013-05-05 01:59 VZ, revision 73928

Fix event handling order in doc/view framework. Ensure that the events are always (provided there is an open document) processed in the following order: 1. wxDocument 2. wxView 3. wxDocManager 4. wxDocChildFrame 5. wxDocParentFrame 6. wxApp Do this by forwarding the events from wxDocParentFrame to wxDocChildFrame first and forward them from there to wxDocManager which -- and this part remains unchanged -- in turn forwards them to the active wxView which finally forwards them to wxDocument. This requires another condition in the event handling code as we still must forward from wxDocParentFrame to wxDocManager itself if there are no active children at all, but this is the only way to have the same event order in all cases, whether the event is originally received by wxDocChildFrame or wxDocParentFrame. Document this and add a unit test verifying that things indeed work like this. See #14314.

2013-05-05 01:59 VZ, revision 73927

Forward events to active child at MSW, not wx, level in wxMDIParentFrame. We want to handle menu (and toolbar) events in the active MDI child before handling them in the parent frame itself and the existing code achieved this by forwarding wxEVT_MENU events at wx event processing level to the active child. However this was not enough as the underlying MSW WM_COMMAND message was still sent to the parent frame only and this could result in wx event not being generated at all if the parent frame had a disabled menu item with the same ID as (an enabled) item in the child frame, see #14314. So forward WM_COMMAND directly to ensure that the correct window gets the event in the first place. And this makes wxEVT_MENU forwarding in TryBefore() unnecessary.

2013-05-05 01:59 VZ, revision 73926

Factor out functions dealing with menus in the event propagation test. No real changes, just refactor the code to allow testing for menu events in other frames too.

2013-05-05 01:59 VZ, revision 73925

Add public wxDocManager::GetAnyUsableView(). This method tries to find the current view harder than GetCurrentView() and always returns a non-NULL view if there are any open documents at all. This is used by wxDocManager internally to find the view to apply the user commands to and will also be needed in the upcoming changes outside of wxDocManager, so just make this method public, as it seems that it could be useful in user code too, especially if we could use some better fallback than the first opened document (e.g. the last document the user interacted with would be better). This also clarifies the confusion between GetCurrentView() and GetActiveView(), see #13296.

2013-05-05 01:59 VZ, revision 73924

Use correct line numbers in assert failures in event propagation test. Replace the calls to CheckMenuEvent() helper with ASSERT_MENU_EVENT_RESULT() macro to allow passing the correct line number to cppunit assertion function, otherwise the line number of CheckMenuEvent() was always used in case of failure.

2013-05-05 01:59 VZ, revision 73923

Consistently set wxMenuBar parent in all ports. Previously, wxGTK used the associated frame as wxMenuBar parent, while the other ports did not. Do set the frame as menu bar parent in all ports now. Of course, considering that wxMenuBar is not a window at all, this doesn't necessarily make much sense, but at least it makes the behaviour consistent.

2013-05-05 01:59 VZ, revision 73922

Pass menu events to the handler in the associated menu bar. We handled the menu events in the menu itself and the associated window, but not in the menu bar that the menu belonged to. This was unexpected, so allow handling the events in the menu bar itself too. Closes #15095.

2013-05-05 01:59 VZ, revision 73921

Fix menu event handlers calling order. Pass the menu event to the window associated with the menu first, before falling back on wxApp. This required adding yet another flag to keep state in wxEvent but it seems to be unavoidable as wxMenuBase::SendEvent() calls ProcessEvent() twice and we must have some way to distinguish the first call from the second one. Added a test case verifying that the menu events are indeed processed in the expected order.

2013-05-03 00:08 VZ, revision 73906

Mention using wxString::c_str() with vararg functions in the change log. This is sufficiently important to be mentioned here in addition to the main documentation. Especially considering that this results in run-time crashes instead of (just) compile-time errors with MSVC.

2013-05-03 00:08 VZ, revision 73905

Expand wxString overview and document some problems due to its dual nature. Explain the possible problems with wxString due to its dual Unicode/ASCII nature. Also document the various conversions in the overview itself. Closes #14694.

2013-05-01 22:53 VZ, revision 73899

Copy max width of wxGridCellTextEditor when cloning it. Previously the max number of characters that could be entered into the editor was lost when it was cloned, making it impossible to really limit the user entry. Closes #15175.

2013-05-01 22:53 VZ, revision 73898

Remove the apparently unneeded wxPGPropArgCls default ctor. This ctor didn't initialize the flags correctly and could result in a crash when a default constructed object was destroyed. Closes #15174.

2013-04-30 22:23 RD, revision 73897

export wxRichTextObjectPtrArrayArray since it is used in the public API.

2013-04-30 22:23 RD, revision 73896

Richtext interface fixes and additions for Phoenix

2013-04-30 22:23 RD, revision 73895

Richtext interface fixes and additions for Phoenix

2013-04-30 22:07 RD, revision 73892

Documentation tweaks for wxFontInfo

2013-04-30 22:07 RD, revision 73891

Add wxICON_AUTH_NEEDED

2013-04-30 17:39 VZ, revision 73890

Compilation fix for wxFont in wxGTK1. wx/encinfo.h is not included from wx/wx.h so include it explicitly. This is the same change as was done in r73519 for wxX11/wxMotif.

2013-04-30 13:13 VZ, revision 73889

Fix wxFont test compilation after wxFont(int flags) ctor removal. Also mention this incompatible (since 2.9.4) change in the change log.

2013-04-30 12:36 VZ, revision 73888

Use WXUNUSED() to suppress unused parameter warnings. Just suppress a harmless warning in wxCarbon build.

2013-04-30 12:36 VZ, revision 73887

Work around harmless g++ warning about possible uninitialized variable. Return from the function before using the variables in the (impossible) case they are actually not initialized.

2013-04-30 12:35 VZ, revision 73886

Add a trivial virtual dtor to suppress g++ warnings. Add a useless but virtual dtor to ValidationTraverserBase private class to avoid g++ warnings.

2013-04-30 12:27 VZ, revision 73885

Add wxFontInfo class to allow using named parameters for wxFont creation. This helper class allows to create wxFonts using shorter and more readable code, e.g. wxFont font(12, wxFONTFLAG_DEFAULT, wxFONTSTYLE_NORMAL, wxFONTWEIGHT_NORMAL, true, "DejaVu Sans"); can now be written simply as wxFont font(wxFontInfo(12).FaceName("DejaVu Sans").Underlined()); Remove the ctor from font flags added in r70445 as it's not needed any longer now that we have this one and adding it resulted in compilation errors in the existing code which compiled with 2.8 because of ambiguities between that ctor and wxFont(int size, int family, int style, int weight. bool underlined, ...) one, e.g. wxFont(12, wxFONTFAMILY_SWISS, wxNORMAL, wxNORMAL) didn't compile any more but it does compile again now. See #9907.

2013-04-30 12:27 VZ, revision 73884

Allow using wxDEFAULT as font size in wxOSX. Using wxDEFAULT as the font size in wxOSX resulted in creating 70pt font, change this to use the normal font size instead for compatibility with the other platforms. Also allow using -1 as wxDEFAULT for compatibility with wxGTK, see #12541.

2013-04-30 01:53 VZ, revision 73881

Fix VC6 compilation after r73880. Work around the broken scoping for the variables declared inside for loops in this compiler by declaring the loop variable once for all loops.

2013-04-30 01:13 VZ, revision 73880

Fix assert when adding items with bitmaps wxBitmapComboBox. The change of r73567 resulted in an assert when adding items with bitmaps to wxBitmapComboBox without object client data. Fix the code added by this commit to work for all kinds of client data, including wxClientData_None. See #14892.

2013-04-30 01:00 VZ, revision 73879

Trying to blindly fix WebTestCase unit test failure. Navigate to about:blank initially, not "about:".

2013-04-29 14:54 VZ, revision 73878

Add empty paragraph in wxRichTextTable::AddColumns() and AddRows(). Do the same thing in Add{Columns,Rows}() as in CreateTable() to ensure the proper cell creation. Closes #15153,

2013-04-29 14:54 VZ, revision 73877

Add support for wxICON_AUTH_NEEDED to wxMessageDialog. Allow showing the standard "Authentication needed" dialog in the message boxes under MSW. Closes #15121.

2013-04-28 20:25 VZ, revision 73876

Really fix the problem with caret in wxGrid text editor under MSW. The problem (see #11681) was due to not allowing the native control handle the focus loss event. This, in turn, was due to the changes of r58969 which tried to work around a crash which happened if the grid was destroyed from the code of one of the user-defined event handlers called during the editor dismissal. Fix both problems at once by calling event.Skip() in OnKillFocus() to let the native handler have the event too and postponing the editor dismissal a little by calling DisableCellEditControl() indirectly from a posted event handler instead of immediately. As this reverts the now unnecessary changes of r64646, it closes #15162.

2013-04-28 20:25 VZ, revision 73875

No real changes, just make wxGridCellEditor accessors const. IsCreated(), GetControl() and GetCellAttr() should both be const, so make them so.

2013-04-26 22:00 VZ, revision 73870

wxOSX: store the menu title when inserting it in the menu bar. We "lost" the menu title if the menu was inserted, and not appended, to the menu bar, resulting wxMenuBar::GetMenuLabel[Text]() returning empty strings for it in this case.

2013-04-26 21:41 VZ, revision 73869

Remove "Windows only" mention from wxTE_PROCESS_ENTER documentation. This style works for wxComboBox under GTK and OS X as well.

2013-04-26 21:41 VZ, revision 73868

Test wxTE_PROCESS_ENTER in the combobox page of the widgets sample. Remove the unused "File name" checkbox in this page and put "Process Enter" one in its place to allow toggling wxTE_PROCESS_ENTER interactively to test whether it works as expected.

2013-04-26 21:41 VZ, revision 73867

Minor visual enhancement in the combobox page of the widgets sample. Expand the lower static box to align it with the upper one, otherwise they look really ugly, especially under Mac.

2013-04-26 18:48 RD, revision 73866

revert part of last change, run configure from the builddir or cwd, not from configure's location.

2013-04-26 08:37 RD, revision 73856

Add wxEVT_DIRCTRL_CHANGED

2013-04-26 08:37 RD, revision 73855

Changes needed to help builder.py be more generic and working well with other modules

2013-04-25 15:16 VZ, revision 73854

Fix generic wxDataViewToggleRenderer hit testing with any alignment. This change reverts the changes of r73835 and r73838 to wxDataViewToggleRenderer::WXActivateCell() and instead fix the bug with mouse hit testing in this function in the wxDataViewMainWindow::OnMouse() itself. The problem there was that it offset the coordinates of the event differently depending on whether the column alignment was set or left as default. Now always make the coordinates relative to the item (not cell) rectangle for compatibility with GTK+ native version, which is enough to make the original, i.e. before the changes of r73835, code work. See #15144.

2013-04-25 14:54 VZ, revision 73853

Fix compilation-breaking typo in the previous commit. s/LoadUrl/LoadURL/

2013-04-25 14:53 VZ, revision 73852

Fix wxWebView test setup failure under OS X. Call LoadUrl() after associating our custom event handler with the browser object as otherwise the wxEVT_WEBVIEW_LOADED event could be generated before we were set up to catch it, resulting in the assertion failure inside ENSURE_LOADED.

2013-04-25 13:56 VZ, revision 73851

Fix wxEVT_DATAVIEW_COLUMN_HEADER_RIGHT_CLICK event type name. Fix incorrect conflict resolution between the changes of r73823 and r73850: the first renamed wxEVT_COMMAND_DATAVIEW_COLUMN_HEADER_RIGHT_CLICKED to wxEVT_COMMAND_DATAVIEW_COLUMN_HEADER_RIGHT_CLICK while the latter renamed it to wxEVT_DATAVIEW_COLUMN_HEADER_RIGHT_CLICKED. The proper new name is wxEVT_DATAVIEW_COLUMN_HEADER_RIGHT_CLICK, use it instead.

2013-04-25 12:11 VZ, revision 73850

Provide shorter synonyms for wxEVT_XXX constants. Use the same short names as are used by the event table macros for the event type constants themselves. This makes them much more comfortable to use, e.g. Bind(wxEVT_BUTTON) compared to Bind(wxEVT_COMMAND_BUTTON_CLICKED). The old long names are still kept for backwards compatibility and shouldn't be removed as it doesn't really cost anything to continue providing them, but all new event types should only use the short versions. Closes #10661.

2013-04-25 11:35 VZ, revision 73849

Small fixes after wxHtmlTagHandler::GetParser() addition. Amend the changes of r73839: - Don't use covariant return type for wxHtmlWinTagHandler::GetParser() as VC6, which we still support, doesn't like it. Besides, this seems unnecessary. - Don't make GetParser() virtual at all as this doesn't appear to be necessary neither. - Add "@since 2.9.5" to the documentation of the new method.

2013-04-24 11:01 VZ, revision 73848

Fix showing back hidden columns and rows in wxGrid. While we don't support auto-sizing of the hidden columns and rows, we need to still show them back when SetColSize() or SetRowSize() is called with -1 (a.k.a. wxGRID_AUTOSIZE) argument.

2013-04-24 04:40 RD, revision 73841

Add documentation for some additional cell types so they can be seen in Phoenix

2013-04-24 04:40 RD, revision 73840

Add ctor for wxHtmlWinTagHandler

2013-04-24 04:40 RD, revision 73839

Add GetParser methods for the tag handlers

2013-04-23 13:56 VZ, revision 73838

Really fix hit testing in the generic wxDataViewToggleRenderer. The changes of r73835 fixed hit testing in horizontal direction but broke it in the vertical one as the computed checkbox rectangle was not relative to the cell rectangle as it should have been. Do fix this now. See #15144.

2013-04-22 12:45 VZ, revision 73837

Add wxSocketBase::GetSocket(). Provide direct access to the underlying socket descriptor. Closes #8829.

2013-04-22 02:32 VZ, revision 73836

Add test for correct short/long file names in wxDir. Verify that enumerating the files using the pattern *.foo doesn't match *.foo.bar files, as it used to do under MSW. See #3432.

2013-04-21 19:39 VZ, revision 73835

Fix hit testing in generic wxDataViewToggleRenderer. Handle clicks on the checkboxes in generic wxDataViewCtrl correctly by taking into account that the checkbox rectangle is centred inside the total cell rectangle. Closes #15144.

2013-04-21 19:18 VZ, revision 73834

Reset sorting column in generic wxDataViewCtrl properly. We could keep using the column previously used for sorting even after UnsetAsSortKey() was called on it. Ensure that this doesn't happen by resetting the owner wxDataViewCtrl sort column index too. Closes #15160.

2013-04-21 00:13 VZ, revision 73832

Add wxTextEntryDialog::SetMaxLength(). Allow restricting the maximal number of characters that can be entered in wxTextEntryDialog. Closes #15158.

2013-04-21 00:13 VZ, revision 73831

Standardize on using "Added" instead of "Add" in the change log. As all the other verbs were used in the infinitive and not past tense, do the same thing for this one too, especially as we already had a mix of both forms.

Select page:

[] [1 14 26 39 40 41 42 43 264 484 705] []

Imprint