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 110 219 328 329 330 331 332 1161 1989 2818] []

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

2011-05-16 16:07 VZ, revision 67754

Ensure that we never return negative client size. wxMSW could return negative client size for tiny windows with borders, this was unexpected and shouldn't happen so explicitly ensure it does not. Also add a unit test to check that this problem doesn't exist in other ports. Closes #13184.

2011-05-16 12:01 VZ, revision 67753

No changes, just refactor the code in MSW wxGetOsDescription() slightly. Construct the description string from several pieces: the OS name, its build number and any extra information about it, instead of duplicating the code appending the build number to the name in several places.

2011-05-16 12:01 VZ, revision 67752

Recognize Windows 7 and Server 2008 versions in wxGetOsDescription(). Use marketing names for these systems instead of just describing them as "Window NT x.y". Closes #13220.

2011-05-15 18:16 VZ, revision 67751

Allow dragging floating AUI frames by the gripper. Previously starting to drag a pane by its gripper worked but once it undocked it was impossible to drag it by the gripper any more which was annoying for the user and unexpected. Fix this by ensuring that we move the correct top level window and not the child window when dragging floating panes. Closes #13177.

2011-05-14 16:18 VZ, revision 67745

Fix small error in floating AUI frames client size under wxMSW. The client size of the floating frames ended up being wrong because we changed the wxRESIZE_BORDER flag after setting it and this changed it (at least under MSW). Reset wxRESIZE_BORDER first now and set the client size correctly afterwards. Closes #13043.

2011-05-14 16:18 VZ, revision 67744

Fix restoring of wxAuiManager::m_has_maximized when restoring perspective. If the perspective being loaded contains a maximized pane, set the m_has_maximized flag to true. Otherwise the flag and the effective pane state was out of sync resulting in several problems in the UI behaviour. Closes #12527.

2011-05-14 16:18 VZ, revision 67743

Correct the drawing of check tools with a drop down button in wxAuiToolBar. This combination was simply not covered by the existing code, add the missing DrawDropDownButton() call. Closes #11139.

2011-05-14 16:18 VZ, revision 67742

Reset the checked state of the first radio item in wxAuiToolBar too. Fix the condition of the loop in wxAuiToolBar::ToggleTool() to also uncheck the item with index 0 that was always excluded before because of "i > 0" check in the loop. Also exclude the item being turned on itself from the loops, it's useless to reset its checked state only to turn it on again below. Closes #11110.

2011-05-14 16:18 VZ, revision 67741

Check for NULL pane window in wxAuiManager. Check that the AUI pane has a non-NULL associated frame before checking whether it's shown. This should fix a crash which could happen when docking an undocked toolbar. Closes #10926.

2011-05-14 16:18 VZ, revision 67740

Improve checking for the landing point when docking windows in wxAUI. This is especially important for multiple monitor setups in which the old code could result in false positives and suggest docking a window on a wrong display. Closes #10612.

2011-05-14 16:17 VZ, revision 67739

Draw wxAuiToolbar button text even if it has no bitmap. Don't skip drawing the button label if it doesn't have any bitmap. Closes #10303.

2011-05-14 16:17 VZ, revision 67738

Take the AUI floating title bar height into account when dragging it. The cursor wasn't positioned correctly when a floating toolbar was dragged by pressing the mouse over its gripper because its position didn't take into account the difference between the client and window coordinates of the floating window (which is basically the height of the window title bar). Notice that the same problem still remains when starting to drag a docked toolbar as it doesn't have the title bar initially but does have it later so the same fix should probably be applied when we reparent the toolbar. Closes #9984.

2011-05-14 16:17 VZ, revision 67737

Cancel dragging in wxAuiNotebook on capture loss. Don't leave the display and internal variables in inconsistent state when the mouse capture is lost while a notebook page is being dragged (as can happen if Alt-Tab is pressed under Windows, for example). Closes #9976.

2011-05-13 15:30 VZ, revision 67735

Don't use the standard containers by default. Revert the change of wxUSE_STD_CONTAINERS to 1 by default as this introduces more incompatibilities which risk hamper upgrading to 3.0 unnecessarily. Update the documentation to better explain why do the non-standard container classes exist in wxWidgets and, especially, that they shouldn't be used when possible. Also document the differences between the normal and STL containers build in the manual.

2011-05-13 15:30 VZ, revision 67734

Fix the comparison function in the list control sample to do what it says. The comment in the function implied that it exchanged the items but in fact it did not and kept their existing order instead. Do revert them now, at least like this something visibly happens in the sample when the items are sorted.

2011-05-13 15:30 VZ, revision 67733

Make wxListCtrl sort function take wxIntPtr, not long, arguments. As the arguments to the sort function contain the client data associated with the items, they may be pointers and hence of greater size than long in Win64 builds. Use wxIntPtr instead of long everywhere to fix this. Notice that this doesn't break compatibility for 32 bit code where long can still be used as it is the same as wxIntPtr there after the previous commit. Closes #4309.

2011-05-13 15:29 VZ, revision 67732

Define wx[U]IntPtr as long, not [s]size_t, in 32 bit builds. Defining wxIntPtr as ssize_t or long in 32 bit builds doesn't really change anything but using long means that we can replace longs in the existing API with wxIntPtr without breaking compatibility, like in wxListCtrl::SortItems(). It is also more compatible with 64 bit builds where wxIntPtr is long already. So it has some minor advantages and no apparent drawbacks.

2011-05-13 15:29 VZ, revision 67731

Remove duplicated portability warning from wxShowEvent description. The warning about this event not being generated by all ports was already present, remove the second copy.

2011-05-13 13:24 DS, revision 67730

Fixed wxUSE_STD_DEFAULT==0 compilation. ScintillaWX.cpp didn't compile because std::string is unknown. Include <string> in case the defines that (by default) are set to wxUSE_STD_DEFAULT are 0.

2011-05-11 20:03 JC, revision 67729
  • D /wxWidgets/branches/SOC2011_GTK3/test.txt

This is a test

2011-05-11 20:02 JC, revision 67728

2011-05-11 18:45 JS, revision 67727

wxRTC doc updates

2011-05-11 18:44 JS, revision 67726

Use more appropriate border style

2011-05-11 17:52 VZ, revision 67725

Don't document wxFileSystemWatcher::AddTree() as pure virtual. It isn't. See #12847.

2011-05-11 08:46 SC, revision 67724

separating observers for default mode (outer 'normal' loop) and common mode loops, fixes #13208

Select page:

[] [1 110 219 328 329 330 331 332 1161 1989 2818] []

Imprint