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 29 58 86 87 88 89 90 999 1909 2818] []

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

2014-03-29 14:03 VS, revision 76208

OS X: fix wxFileDialog::SetupExtraControls()'s sandbox test. OS X 10.9 (possibly earlier) don't have nil contentView in NSSavePanel anymore, a NSRemoteView instance is used. The wx code that follows this test still crashes under sandbox, though, so update the check to use the APP_SANDBOX_CONTAINER_ID environment variable, which is only set when running under the sandbox. This is just another quick fix for the existing uncomfortably long-lived sandbox crash hotfix, not a proper solution.

2014-03-29 14:03 VS, revision 76207

Don't emit wxEVT_TEXT in wxMSW's wxTextCtrl::SetFont(). Native text control sends EN_CHANGE when the font changes, producing a wxEVT_TEXT event as if the user changed the value. This is not the case, so supress the event.

2014-03-29 14:02 VS, revision 76206

OS X: fix wxFileDialog::SetupExtraControls()'s sandbox test. OS X 10.9 (possibly earlier) don't have nil contentView in NSSavePanel anymore, a NSRemoteView instance is used. The wx code that follows this test still crashes under sandbox, though, so update the check to use the APP_SANDBOX_CONTAINER_ID environment variable, which is only set when running under the sandbox. This is just another quick fix for the existing uncomfortably long-lived sandbox crash hotfix, not a proper solution.

2014-03-27 23:10 VZ, revision 76205

Make "NOT the index" in wxListCtrl::SortItems() stand out even more. Any reasonable person expects the sort callback to receive the indices of the items, but it doesn't: it's passed the client data associated with them instead. Make it even more noticeable in the documentation.

2014-03-27 13:46 JS, revision 76204

Allow derivation from wxRichTextBufferDataObject

2014-03-27 13:05 VZ, revision 76203

Russian translations update from Pavel Maryanov.

2014-03-27 01:02 VZ, revision 76202

Make wxMSW owner drawn menu item code more clear and correct. The user-visible effect of this change is that removing the item from the menu and adding it back doesn't lose its icon any more. At the code level, wxMenuItem::SetBitmaps() and related methods are implemented outside of "#if wxUSE_OWNER_DRAWN" which allows to use them even in minimalistic library builds. And IsOwnerDrawn() is not used any more to determine whether the item has bitmaps, just only if it's really owner drawn, making the code more clear and fixing at least the bug above and possible more. Closes #13878.

2014-03-27 01:02 VZ, revision 76201

Rename wxMenuItem::MustUseOwnerDrawn() to MSWMustUseOwnerDrawn(). No real changes, just make it clear that this method is MSW-specific and is about using owner drawn items at MSW level and not wx one. See #13878.

2014-03-27 01:02 VZ, revision 76200

Close monitoring thread handles as soon as possible in wxMSW. Don't leave the handles of all threads used for monitoring the child processes open until the main process termination, rather close them as soon as the monitored process terminates. This ensures that we don't accumulate potentially unbounded number of open handles if we keep launching new child processes. An even better idea would be to actually use a single thread for monitoring all of them, but this fix is much simpler and should fix the most acute problem for now. Closes #16123.

2014-03-27 00:41 VZ, revision 76199

Close monitoring thread handles as soon as possible in wxMSW. Don't leave the handles of all threads used for monitoring the child processes open until the main process termination, rather close them as soon as the monitored process terminates. This ensures that we don't accumulate potentially unbounded number of open handles if we keep launching new child processes. An even better idea would be to actually use a single thread for monitoring all of them, but this fix is much simpler and should fix the most acute problem for now. Closes #16123.

2014-03-26 14:40 VZ, revision 76198

Dutch translations update from Thomas De Rocker.

2014-03-24 19:46 VZ, revision 76197

Add missing wxUSE_WXDIB checks. Fix compilation with wxUSE_WXDIB==0. Closes #16113.

2014-03-24 19:46 VZ, revision 76196

Don't change bitmap depth in wxMSW when copying it. Sometimes, creating a DDB may fail to create the bitmap of the requested depth and so a copy of wxBitmap could have a different depth than the original wxBitmap. Avoid this problem by falling back on using DIB if DDB with the right depth couldn't be created. Closes #11640.

2014-03-24 14:19 VZ, revision 76195

Add "View text" menu item to the webview sample. Allow to view just the text of the web page. Closes #16098.

2014-03-24 14:17 VZ, revision 76194

Fix reentrancy issues in wxMSW wxTextCtrl max length handling code. The changes of r75936 didn't work correctly if the handler of wxEVT_TEXT in some text control modified a (potentially) different text control, as the same global variable was reused with disastrous results. Avoid this by keeping a stack of insertion lengths instead. Additionally, fix another problem in r75936 which used 0 as a special marker for the insertion length, which result in redoing each insertion of empty string (which is another word for Remove()) twice unnecessarily, by using -1 instead. Closes #15980.

2014-03-24 14:06 VZ, revision 76193

Fix reentrancy issues in wxMSW wxTextCtrl max length handling code. The changes of r75940 didn't work correctly if the handler of wxEVT_TEXT in some text control modified a (potentially) different text control, as the same global variable was reused with disastrous results. Avoid this by keeping a stack of insertion lengths instead. Using a per-control field would work too, but would be a bit wasteful as the size of the stack will rarely be more than 1 (and never much more) and this change can also be applied to 3.0 branch without breaking ABI. Additionally, fix another problem in r75940 which used 0 as a special marker for the insertion length, which result in redoing each insertion of empty string (which is another word for Remove()) twice unnecessarily, by using -1 instead. Closes #15980.

2014-03-23 18:54 VZ, revision 76192

Add files included by richtext library to MSVC1{1,2} projects. Closes #16104.

2014-03-23 16:18 VZ, revision 76191

Fix setting menu item bitmaps after appending them in wxMSW. Update the bitmap used by Windows when using non-owner-drawn items with bitmaps. Closes #9388.

2014-03-23 16:18 VZ, revision 76190

Refactor wxMSW: move some code from wxMenu to wxMenuItem. This will allow reusing it for other wxMenuItem bitmap-related operations. See #9388.

2014-03-23 01:57 VZ, revision 76189

Fix toolbar repainting after deleting a tool in wxMSW. The toolbar was in an inconsistent state when recalculating the sizes of the separators used as placeholders for the controls and stretch spacers as the tool was already deleted from the native toolbar but still present in wx internal toolbar data and this resulted in discrepancies between the indices in the native and wx toolbars. Fix this by specially marking the already deleted but not yet removed tool and ignoring it during the recalculations. This makes the old, and only partially successful, attempt to work around this bug in DoDeleteTool() unnecessary and so the code is actually simplified by this change. Closes #16095.

2014-03-23 01:57 VZ, revision 76188

Document what wxPrintQuality really is. Mention that it can be either a predefined constant or a number expressing the resolution. See #14085.

2014-03-23 01:57 VZ, revision 76187

Fix wxFileSystemWatcher::RemoveAll() to actually work. We need to call DoRemove() on all watcher objects to really remove them, just removing our record of them was not enough and e.g. resulted in errors if we tried to re-add a previously watched path again. Closes #15531.

2014-03-23 01:57 VZ, revision 76186

Fix handling deletion of watched directory in MSW wxFileSystemWatcher. Don't log an incomprehensible error when the watched directory itself is deleted, but generate wxFSW_EVENT_DELETE for it. This is consistent with the behaviour under Unix and generally more useful. Closes #13294.

2014-03-23 01:57 VZ, revision 76185

Small refactoring in wxFileSystemWatcher MSW implementation. Make wxIOCPService::GetStatus() smarter about its return value, it makes sense to encapsulate the convention used to indicate the thread exit condition inside wxIOCPService class itself instead of sharing it between it wxIOCPThread itself. It will also make it easier to detect more detailed error conditions in this code.

2014-03-23 01:56 VZ, revision 76184

Disable the use of "override" keyword for MSVC < 11. While the keyword is indeed supported since MSVC 8, it's only since MSVC 11 that using it doesn't generate C4481 compiler warning ("nonstandard extension used"), so avoid using it with the earlier versions. See #16100.

Select page:

[] [1 29 58 86 87 88 89 90 999 1909 2818] []

Imprint