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 54 107 160 161 162 163 164 1049 1933 2818] []

Changes per page:

25 50 100 250 500 1000 2000

Changelog for wxWidgets (70435 changes):

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.

Select page:

[] [1 54 107 160 161 162 163 164 1049 1933 2818] []

Imprint