Changelogs

Overview

These changelogs reflect the history of all files in the Subversion repository. The changelog has been generated at 2015-03-02 07:18:01

Select Changelog:

FileZilla 3, FileZilla,
FileZilla Server, wxWidgets

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

2014-02-21 22:47 VZ, revision 75968

Basque translations update for 3.0.1 from Xabier Aramendi.

2014-02-21 22:47 VZ, revision 75967

Basque translations update for 3.0.1 from Xabier Aramendi.

2014-02-21 20:05 SC, revision 75966

make sure a frozen control calls a native 'thaw' on the tlw during destruction, otherwise tlws might end up unresponsive, see #16011

2014-02-21 18:15 VZ, revision 75965

Ukrainian translations update for 3.0.1 from Yuri Chornoivan.

2014-02-21 18:15 VZ, revision 75964

Ukrainian translations update for 3.0.1 from Yuri Chornoivan.

2014-02-21 17:28 VZ, revision 75963

French translations update for 3.0.1 from Xavier Perrissoud. Apply to the trunk as well. See #16013.

2014-02-21 17:27 VZ, revision 75962

Regenerate all .po files in the trunk too. Bring them (more) in sync with 3.0 branch.

2014-02-21 17:22 VZ, revision 75961

French translations update for 3.0.1 from Xavier Perrissoud. Closes #16013.

2014-02-21 14:55 VZ, revision 75960

Regenerate message catalogs for 3.0.1 release. Add a couple of new strings which have been added since 3.0.0.

2014-02-21 01:51 VZ, revision 75959

Fix memory leak in wxRibbonToolBar in case of error. Use wxScopedPtr to ensure the tool is not leaked, even if we fail to insert it.

2014-02-21 01:51 VZ, revision 75958

Fix uninitialized variable use in wxPropertyGrid code. wxPGProperty::GetItemAtY() uses its input/output "nextItem" parameter, so it must be initialized before calling it.

2014-02-21 01:51 VZ, revision 75957

Ensure we don't read invalid memory in wxOSX wxDisplay code. Replace wxASSERT() with wxCHECK_MSG() to ensure that we don't read beyond the end of the array even if we are given an invalid index.

2014-02-21 01:51 VZ, revision 75956

Fix memory leak on error return in wxOSX wxDisplay code. Use wxScopedArray to ensure that memory is freed, even if wxCHECK_MSG() condition fails.

2014-02-21 01:51 VZ, revision 75955

Fix memory leak in case of error in wxOSX graphics code. Delete the pointer before returning from the function if we don't pass its ownership to CGDataProviderCreateWithData().

2014-02-21 01:51 VZ, revision 75954

Fix memory leak on error return from wxMsgCatalogFile::FillHash(). Use wxScopedPtr to make memory management simpler and to ensure that all pointers allocated in this function are deleted: this wasn't the case when we returned false earlier due to the MO file being invalid.

2014-02-21 01:51 VZ, revision 75953

No real changes, just use smart pointers in GIF decoding code. Use wxScopedArray to make the code much shorter and guarantee that it doesn't leak memory.

2014-02-21 01:51 VZ, revision 75952

Fix socket leak in Accept() in case of error.o We leaked a socket descriptor if creating the accepted socket object failed.

2014-02-21 01:51 VZ, revision 75951

Fix fall back to default resolution in wxOSX printing code. The code was written to use the default resolution if getting it from the printer failed but only handled failure of PMPrinterGetOutputResolution() and not of PMSessionGetCurrentPrinter() itself. Use default resolution if obtaining it failed for any reason (alternative could be to return error if obtaining it failed for any return...).

2014-02-21 01:51 VZ, revision 75950

Correct wxDataViewColumn::AppendXXXColumn() return value in case of failure. Don't return invalid column pointer if it was freed because actually appending it to the control failed. Fixes corresponding Coverity warnings.

2014-02-20 16:13 VZ, revision 75949

Fix crash when using wxThreadSpecificInfo from global object ctor. When not using compiler TLS support (which is the default now), TLS variable itself needs to be initialized and user-defined code in the global objects ctor could be called before this happened, resulting in using uninitialized CRITICAL_SECTION under Windows and a crash. Fix this by wrapping global wxThreadSpecificInfo itself in an accessor function ensuring that it is always initialized before use. Notice that this required adding wxTLS_TYPE_REF() as wxTLS_TYPE() itself can't be used for the function return value (__thread or similar can only be used on the variables). Closes #16009.

2014-02-20 16:12 VZ, revision 75948

Fix crash when using wxThreadSpecificInfo from global object ctor. When not using compiler TLS support (which is the default now), TLS variable itself needs to be initialized and user-defined code in the global objects ctor could be called before this happened, resulting in using uninitialized CRITICAL_SECTION under Windows and a crash. Fix this by wrapping global wxThreadSpecificInfo itself in an accessor function ensuring that it is always initialized before use. Notice that this required adding wxTLS_TYPE_REF() as wxTLS_TYPE() itself can't be used for the function return value (__thread or similar can only be used on the variables). Closes #16009.

2014-02-20 14:06 VZ, revision 75947

Use correct column type when adding columns to wxDataViewListCtrl. Using base class methods such as AppendBitmapColumn() resulted in wxDataViewListCtrl::AppendColumn() being called but this function always assumed the column was of "string" variant type -- which was, of course, false for bitmap columns and so resulted in heap corruption (thanks to the wonderfully type unsafe code using wxVariant) and a crash. Get the correct type to use from the column itself now to fix this. Closes #16008.

2014-02-20 14:05 VZ, revision 75946

Use correct column type when adding columns to wxDataViewListCtrl. Using base class methods such as AppendBitmapColumn() resulted in wxDataViewListCtrl::AppendColumn() being called but this function always assumed the column was of "string" variant type -- which was, of course, false for bitmap columns and so resulted in heap corruption (thanks to the wonderfully type unsafe code using wxVariant) and a crash. Get the correct type to use from the column itself now to fix this. Closes #16008.

2014-02-20 01:32 VZ, revision 75945

Don't show hidden MDI frames when maximizing them in wxMSW. This is inconsistent with the other ports and rather unexpected. Closes #2508.

2014-02-20 01:32 VZ, revision 75944

Don't show the MDI children implicitly by default in wxMSW any more. We kept doing it for compatibility with pre-2.5.3 versions but this was a long time ago and we don't need this any longer. See #2508.