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 39 76 114 115 116 117 118 548 979 1409] []

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

2012-05-04 01:30 RD, revision 71347

fix incorrect default values

2012-05-03 12:17 VZ, revision 71346

Document wxDataViewChoiceByIndexRenderer. At least briefly document this class too and not only its parent wxDataViewChoiceRenderer one. Closes #14265.

2012-05-03 12:17 VZ, revision 71345

No changes, just remove duplicate flags checks in wxUniv wxTLW. For some reason (rename of the old wxTHICK_FRAME to wxRESIZE_BORDER?) we tested for wxRESIZE_BORDER twice in a couple of places. Don't do it for clarity. Closes #14264.

2012-05-02 21:38 SC, revision 71344

use explicit WakeUp variant, too many errors using heuristics, fixes #14176

2012-05-02 21:30 SC, revision 71343

make WakeUp variant explicit, too many errors using heuristics, like #14176

2012-05-02 20:44 SC, revision 71342

fixes #14178

2012-05-02 16:44 DS, revision 71341

Fixed parts of toolbar background not being drawn with older comctl32.dll. When using comctl32.dll versions older than 6.0 toolbar icons would not have their background drawn. Fix this in a rough way by always completely erasing the background like was done before. Regression since r62971. Closes #13512.

2012-05-02 12:37 VZ, revision 71340

German translations update from Thomas Krebs. Closes #14262.

2012-04-30 16:51 VS, revision 71336

Fix destruction of wxDataViewCtrl's editor control. Don't pop event handler from the control more than once. See r70002 and r70005 (which this reverts) for reference. Fixes #14215.

2012-04-30 11:33 VS, revision 71335

wxDataViewCtrl: always update the header when col best width changes. Have an explicit per-column dirty flag and use that to determine whether we need to call wxHeaderCtrl::UpdateColumn(). Previously, the lack of computed best width was used as an indicator, but this didn't work correctly if some code called GetWidth() after invalidation but before wxDataViewCtrl::UpdateColWidths() was called at idle time. This resulted in header's column widths getting out of sync with the control itself. Fixes #14167.

2012-04-30 11:33 VS, revision 71334

Invalidate wxDataViewCtrl bests widths on expand/collapse. The best column widths are computed from "realized" items that are available as rows in wxDataViewCtrl. This information changes when a previously collapsed node is expanded and new items become available for column width calculation. Fixes #14167.

2012-04-30 11:33 VS, revision 71333

Respect minimal width in wxDataViewCtrl::GetBestColumnWidth(). See #14167.

2012-04-30 01:48 VZ, revision 71329

Work around the problem with not exiting event loop under MSW. Changes of r71304 broke the event loop termination under MSW, limit them to only the case in which they were really needed, i.e. when loop is really exited by a pending event handler. This is only a temporary solution, we need something better in longer term. See #14250.

2012-04-30 01:22 VZ, revision 71327

No changes, just refactor common IsSorted() tests in wxGTK wxDataViewCtrl. Add wxDataViewCtrlInternal::ShouldBeSorted() helper instead of testing for both IsSorted() and wxDataViewModel::HasDefaultCompare() in several places.

2012-04-30 01:22 VZ, revision 71326

No real changes, just make wxDataViewCtrlInternal::IsSorted() const. This is a simple accessor, should have been const since the beginning.

2012-04-30 01:22 VZ, revision 71325

Use PCH in the tests in all Windows ports and not only when using wxMSW. This change doesn't actually change anything for the "normal" ports as it only affects wxGTK/MSW which is not officially supported yet, so the make/project files are unchanged by it. Closes #14249.

2012-04-30 01:22 VZ, revision 71324

Added wxDataViewEvent::SetDragFlags() and GetDropEffect() methods. Allow specifying the drag operation flags and retrieving the drop effect when it's over for wxDataViewCtrl drag-and-drop. Currently this is only implemented in the generic version. Closes #12583.

2012-04-30 01:22 VZ, revision 71323

Set the data size in wxEVT_COMMAND_DATAVIEW_ITEM_DROP_POSSIBLE in wxGTK. Allow wxEVT_COMMAND_DATAVIEW_ITEM_DROP_POSSIBLE handler to examine the data being dragged by setting not only the pointer to it but also its size, as otherwise it's impossible to do anything with it. See #12583.

2012-04-30 01:22 VZ, revision 71322

Explicitly document wxDrag_XXX flags. They were mentioned in DoDragDrop() documentation but not documented on their own. Do it now to be able to refer to them from elsewhere.

2012-04-30 01:22 VZ, revision 71321

Remove internal only methods from wxDataViewEvent documentation. SetDataXXX() methods are only meant to be used by wxDataViewCtrl itself, so don't document them as part of public API. Their documentation was pretty useless anyhow as it didn't say anything not already contained in the method name.

2012-04-30 01:22 VZ, revision 71320

Restore 2.8 stock labels for wxID_PREVIEW inadvertently changed in 2.9. The wxID_PREVIEW labels were accidentally removed in r68641 and added back with a wrong/different label later. Restore the same one (or almost, just add an ellipsis at the end) that was used in 2.8. Closes #13906.

2012-04-30 01:22 VZ, revision 71319

Add a hack to prevent the test suite from aborting after Grid test case. There is a problem with the native header control still having the mouse capture when the grid is destroyed in wxGTK and this resulted in asserts when destroying the grid, nested asserts due to an exception being thrown from a dtor and finally abort that prevented the rest of the tests from running. As I failed to find the real reason for this problem, just forcefully ensure that we don't have the mouse capture when destroying the grid. This at least allows the complete test suite to run.

2012-04-30 01:22 VZ, revision 71318

Improve error reporting for nested asserts failures in the test suite. If an assert occurred while handling an exception generated by a previous assert handler, the information about the original assert was lost even if though it was more important than the secondary assert. Do preserve and show the original assert message in this case now.

2012-04-30 01:22 VZ, revision 71317

Work around wxDateTime::ParseFormat() problem in generic wxDateTimePickerCtrl. Due to a bug in wxDateTime::ParseFormat(), calling it with wxString::c_str() currently just crashes, so don't do this in generic wxDateTimePickerCtrl code. The real fix is, of course, to correct the bug in wxDateTime itself but for now this at least prevents the crash when executing the test suite. And using c_str() here is unnecessary anyhow. See #14214.

2012-04-30 01:22 VZ, revision 71316

Preserve wxComboBox selection when modifying the selected item in wxGTK too. This does the same thing as r70018 did for wxMSW but for wxGTK, i.e. it keeps the combo box item selected when its text is modified. This fixes [Bitmap]ComboBox unit tests under wxGTK. See #13769.

2012-04-30 01:21 VZ, revision 71315

Enable wxComboBox::SetString() test in the widgets sample. It was disabled because it wasn't implemented for wxGTK at some time in the past -- but it is implemented now, so there is no reason to not allow testing it.

2012-04-29 11:36 VS, revision 71314

Don't use ancient -no-cpp-precomp flag on OS X. See http://trac.wxwidgets.org/ticket/14029 for a discussion of the problems it causes when using non-Apple compiler. Even for Apple's GCC, it does nothing these days and we no longer support OS X 10.3, so there's no point in continuing to use it. Fixes #14029.

2012-04-29 00:25 VZ, revision 71313

Make wxGTK code returning correct focus in popup menu presence more robust. Replace the changes of r69938 with an alternative and simpler solution: instead of playing games with gs_pendingFocus, which could break down if its old value became invalid while the menu was shown as happened if one of the menu commands resulted in this window being destroyed, just take the currently shown popup menu into account in DoFindFocus() itself. This should be safer as there is no danger of any dangling pointers here and is also simpler and more obviously correct. Closes #14103.

2012-04-29 00:25 VZ, revision 71312

Add missing "flags" argument to wxNotificationMessage ctor in wxMSW. It was impossible to specify the flags when creating wxNotificationMessage in wxMSW, cotrary to the other ports and the documentation. Fix this by adding the missing argument to the ctor and simply passing it to the base class one, we don't have to do anything else as the existing code already calls GetFlags() later so it should respect these flags without any more changes. Closes #14245.

2012-04-29 00:25 VZ, revision 71311

Fix crash in wxFileConfig when deleting last entry of the root group. This resulted in keeping a dangling pointer to the group line in wxFileConfigGroup and any attempt to use it after this resulted in a crash. Fix this by explicitly resetting the last line in this case. Also add a unit test for this scenario. Closes #14243.

2012-04-29 00:25 VZ, revision 71310

Make it possible to forward declare wx{Choice,Tool,Tree}bookEvent again. Don't use typedef for these classes as it makes it impossible to forward-declare them, just use #define instead as we already do for wxListbookEvent and wxNotebookEvent. This allows forward declaration and is also more consistent. Closes #12242.

2012-04-29 00:25 VZ, revision 71309

Use generic wxAboutBox() in wxUniv/GTK. The native GTK implementation is not used in wxUniv/GTK, so don't exclude the generic one as well. Notice that the same should be done for wxMSW and wxOSX too but we currently seem to use the native version even in wxUniv there. It would be better to consistently use the generic version in all wxUniv ports. Closes #14236.

2012-04-29 00:25 VZ, revision 71308

Don't change wxTextEntry value if it didn't really change. This is not only unnecessary but also can result in a kind of infinite loop when wxTextEntry::SetValue() is called from wxEVT_IDLE handler as really modifying the text results in another wxEVT_IDLE being generated and another call to SetValue() and so on while not doing it in the first place completely works around the problem and is also more efficient. Closes #13936.

2012-04-29 00:25 VZ, revision 71307

Run some wxTextCtrl unit test cases for single and multi-line controls. Some of the tests that were previously ran for single or multi-line controls only actually apply to both of them, so run them for both kinds of control to test that both of them work correctly.

2012-04-29 00:24 VZ, revision 71306

No changes, just refactor wxTextCtrl unit test case. Allow running the same tests for both single and multi-line controls easily. No real changes yet though, the tests are still ran for the controls with the same styles as before for now.

2012-04-29 00:24 VZ, revision 71305

Recognize wxDefaultDateTime in gdb wxDateTime pretty-printer. Trying to print an uninitialized/invalid wxDateTime in gdb resulted in an error (Python exception from datetime module), recognize it specially now.

2012-04-29 00:24 VZ, revision 71304

Don't block in wxEventLoopManual::Dispatch() if loop was exited. If Exit() was called from a handler for one of the pending events we could reenter Dispatch() and block there indefinitely if no other events were coming and this was exactly what happened in wxFileSystemWatcher unit test, preventing it from ever running to completion under Unix. Fix this by checking m_shouldExit after executing the pending handlers and before calling Dispatch().

2012-04-29 00:24 VZ, revision 71303

Add a gdb pretty-printer for wxFileName objects. This pretty-printer works by calling the C++ wxFileName::GetFullPath() directly instead of interpreting the object data from gdb because this is much simpler to do, so it can only be used when debugging live programs. If this is a serious restriction, it would need to be changed to use gdb data access only later.

2012-04-29 00:24 VZ, revision 71302

Fix harmless warnings about hiding base class virtual in dialogs sample. GetTitle() added in r71213 resulted in virtual function warnings from g++, fix them by renaming it to GetBoxTitle().

2012-04-29 00:24 VZ, revision 71301

Don't use too big width for wxHtmlHelpWindow navigation panel. The width of the navigation panel in wxHtmlHelpWindow could become arbitrarily high if long items used. Avoid this by using a reasonably large but not too big minimal width instead of determining it automatically from the items width. Closes #13754.

2012-04-29 00:24 VZ, revision 71300

Fix erasing wxHtmlWindow background in wxUniv. Prevent the default wxWindow-level wxEVT_ERASE_BACKGROUND handler from being used in wxUniv for wxHtmlWindow. This is unnecessary as it has its own handler anyhow and also doesn't work for some reason as erasing wxMemoryDC by drawing a solid rectangle over it seems to be broken in at least wxX11. Work around this problem by erasing the background in wxHtmlWindow itself if no user-defined (as opposed to any, including one defined in wxWindow itself) handler for this event exists. Closes #13880.

2012-04-29 00:24 VZ, revision 71299

Handle kCGImageAlphaNoneSkipFirst correctly in wxOSX wxBitmap code. The code tested twice for kCGImageAlphaNoneSkipLast which was clearly wrong. The original intention was probably to check for both it and kCGImageAlphaNoneSkipFirst, so fix it to this now. Closes #14019.

2012-04-29 00:24 VZ, revision 71298

Fix wxBitmapButton best size calculation in wxOSX/Carbon. wxAnyButton refactoring broke the best size computation for Carbon, fix it to work as it did before. Closes #13830.

2012-04-29 00:24 VZ, revision 71297

Document the change in wxEVT_SIZE generation for wxDialogs in wxMSW. These events are now generated earlier and can result in crashes if the controls they use are not initialized yet.

2012-04-29 00:24 VZ, revision 71296

Document that wxDCClipper currently resets clipping region. Unlike other similar classes, this one doesn't restore the previous clipping region but just resets it because there is no way to get the current clipping region from wxDC now. At least document this limitation until it can be fixed. See #13834.

2012-04-29 00:12 VZ, revision 71295

German translations update from Mechtilde. Closes #14246.

2012-04-28 00:35 VZ, revision 71289

Added note about WXWIN_COMPATIBILITY_2_6 being off in 2.9 by default. Also list some concrete symbols which are not available any more and their replacements.

2012-04-27 13:39 JS, revision 71287

Restored the exact-fit-button horizontal margin calculation from 2.8 since it was too cramped.

2012-04-26 03:29 RD, revision 71280

Typo fix, and add some missing methods.

2012-04-25 13:42 JS, revision 71277

Fixed floating image layout when typing in subsequent paragraph Now makes use of max size for images and keeps the image size reasonable Added original image size so can usually avoid reloading image when recomputing cached bitmap size Takes into account bottom of the last floating image so scrollbars are set correctly Original image size is shown in disabled size controls

Select page:

[] [1 39 76 114 115 116 117 118 548 979 1409] []

Imprint